View AM79C961AKIW_3255579.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

publication# 19364 rev: d amendment/ 0 issue date: march 2000 am79c961a pcnet ? -isa ii jumperless, full duplex single-chip ethernet controller for isa distinctive characteristics single-chip ethernet controller for the industry standard architecture (isa) and extended industry standard architecture (eisa) buses supports ieee 802.3/ansi 8802-3 and ethernet standards supports full duplex operation on the 10base-t, aui, and gpsi ports direct interface to the isa or eisa bus pin compatible to am79c961 pcnet-isa + jumperless single-chip ethernet controller software compatible with amd ? s am7990 lance register and descriptor architecture low power, cmos design with sleep mode allows reduced power consumption for critical battery powered applications individual 136-byte transmit and 128-byte receive fifos provide packet buffering for increased system latency, and support the following features: ? automatic retransmission with no fifo reload ? automatic receive stripping and transmit padding (individually programmable) ? automatic runt packet rejection ? automatic deletion of received collision frames dynamic transmit fcs generation programmable on a frame-by-frame basis single +5 v power supply internal/external loopback capabilities supports 8k, 16k, 32k, and 64k boot proms or flash for diskless node applications supports microsoft ? s plug and play system configuration for jumperless designs supports staggered at bus drive for reduced noise and ground bounce integrated magic packet ? support for remote wake up of green pcs supports 8 interrupts on chip look ahead packet processing (lapp) allows protocol analysis to begin before end of receive frame supports 4 dma channels on chip supports 16 i/o locations supports 16 boot prom locations provides integrated attachment unit interface (aui) and 10base-t transceiver with 2 modes of port selection: ? automatic selection of aui or 10base-t ? software selection of aui or 10base-t automatic twisted pair receive polarity detection and automatic correction of the receive polarity supports bus-master, programmed i/o, and shared-memory architectures to fit in any pc application supports edge and level-sensitive interrupts dma buffer management unit for reduced cpu intervention which allows higher throughput by by-passing the platform dma jtag boundary scan (ieee 1149.1) test access port interface for board level production test integrated manchester encoder/decoder supports the following types of network interfaces: ? aui to external 10base2, 10base5, 10base-t or 10base-f mau ? internal 10base-t transceiver with smart squelch to twisted pair medium supports lance general purpose serial interface (gpsi) 132-pin pqfp and 144-pin tqfp packages supports shared memory and pio modes supports pcmcia mode (144-tqfp version only) support for operation in industrial temperature range ( ? 40 c to +85 c) available in both packages
2 am79c961a general description the pcnet-isa ii controller, a single-chip ethernet con- troller, is a highly integrated system solution for the pc-at industry standard architecture (isa) architec- ture. it is designed to provide flexibility and compatibil- ity with any existing pc application. this highly integrated vlsi device is specifically designed to re- duce parts count and cost, and addresses applications where higher system throughput is desired. the pc- net-isa ii controller is fabricated with amd ? s advanced low-power cmos process to provide low standby cur- rent for power sensitive applications. the pcnet-isa ii controller can be configured into one of three different architecture modes to suit a particular pc application. in the bus master mode, all transfers are performed using the integrated dma controller. this configuration enhances system performance by allowing the pcnet-isa ii controller to bypass the plat- form dma controller and directly address the full 24-bit memory space. the implementation of bus master mode allows minimum parts count for the majority of pc applications. the pcnet-isa ii can also be config- ured as a bus slave with either a shared memory or programmed i/o architecture for compatibility with low-end machines, such as pc/xts that do not support bus masters, and high-end machines that require local packet buffering for increased system latency. the pcnet-isa ii controller is designed to directly inter- face with the isa or eisa system bus. it contains an isa plug and play bus interface unit, dma buffer man- agement unit, 802.3 media access control function, individual 136-byte transmit and 128-byte receive fifos, ieee 802.3 defined attachment unit interface (aui), and a twisted pair transceiver media attach- ment unit. full duplex network operation can be enabled on any of the device ? s network ports. the pc- net-isa ii controller is also register compatible with the lance (am7990) ethernet controller and pcnet-isa (am79c960). the dma buffer management unit sup- ports the lance descriptor software model. external remote boot and ethernet physical address proms and electrically erasable proms are also supported. this advanced ethernet controller has the built-in capability of automatically selecting either the aui port or the twisted pair transceiver. only one interface is active at any one time. the individual 136-byte transmit and 128-byte receive fifos optimize system over- head, providing sufficient latency during packet trans- mission and reception, and minimizing intervention during normal network error recovery. the integrated manchester encoder/decoder eliminates the need for an external serial interface adapter (sia) in the node system. if support for an external encoding/decoding scheme is desired, the embedded general purpose serial interface (gpsi) allows direct access to/from the mac. in addition, the device provides programmable on-chip led drivers for transmit, receive, collision, receive polarity, link integrity and activity, or jabber status. the pcnet-isa ii controller also provides an external address detection interface tm (eadi tm ) to allow external hardware address filtering in internet- working applications. for power sensitive applications where low stand-by current is desired, the device incorporates a sleep function to reduce over-all system power consumption, excellent for notebooks and green pcs. in conjunction with this low power mode, the pcnet-isa ii controller also has integrated functions to support magic packet, an inexpensive technology that allows remote wake up of green pcs. with the rise of embedded networking applications operating in harsh environments where temperatures may exceed the normal commercial temperature (0 c to +70 c) window, an industrial temperature ( ? 40 c to +85 c) version is available in all two packages; 132-pin pqfp and 144-pin tqfp. the industrial temperature version of the pcnet-isa ii ethernet controller is characterized across the industrial temperature range ( ? 40 c to +85 c) within the published power supply specification (4.75 v to 5.25 v; i.e., 5% v cc ).
am79c961a 3 block diagram: bus master mode 19364b-1 isa bus interface unit rcv fifo xmt fifo fifo control buffer management unit eeprom interface unit 802.3 mac core encoder/ decoder (pls) & aui port 10base-t mau private bus control jtag port control aen dack [3, 5 ? 7] drq[3, 5 ? 7] iochrdy iocs16 ior iow irq[3, 4, 5, 9, 10, 11, 12] master memr memw ref reset sbhe bale sd[0-15] la[17-23] sa[0-19] sleep shfbusy eedo eedi eesk eecs dvdd[1-7] dvss[1-13] avdd[1-4] avss[1-2] dxcvr/ear ci+/ ? di+/ ? xtal1 xtal2 do+/ ? rxd+/ ? txd+/ ? txpd+/ ? irq15/apcs bpcs led [0 ? 3] prdb[0 ? 7] tdo tms tdi tck
4 am79c961a table of contents am79c961a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 distinctive characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 block diagram: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 table of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 standard products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 connection diagrams: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 pqfp 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 pin designations: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 listed by pin number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 pin designations: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 listed by pin name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 pin designations: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 listed by group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 listed by group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 pin description: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 ieee p996 terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 isa interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 aen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 bale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 dack 3, 5-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 drq 3, 5-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 iochrdy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 iocs16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 ior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 iow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 irq 3, 4, 5, 9, 10, 11, 12, 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 la17-23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 memr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 memw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 sa0-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 sbhe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 sd0-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 board interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 irq12/flashwe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 irq15/apcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 bpcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 dxcvr/ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 ledo-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 prdb3-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 prdb2/eedo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 prdb1/eedi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 prdb0/eesk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 shfbusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 eecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 sleep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 xtal1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 xtal2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 connection diagrams: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 pqfp 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 block diagram: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 pin designations: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
am79c961a 5 listed by pin number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 pin designations: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 listed by pin name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 pin designations: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 listed by group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 pin designations: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 listed by group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 pin description: bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 isa interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 aen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 iochrdy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 iocs16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 ior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 iow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 irq3, 4, 5, 9, 10, 11, 12, 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 memr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 memw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 ref . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 sa0-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 sbhe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 sd0-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 board interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 apcs /irq15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 bpam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 bpcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 dxcvr/ear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 led0-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 prab0-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 prdb3-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 prdb2/eedo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 prdb1/eedi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 prdb0/eesk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 shfbusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 eecs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 sleep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 sma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 smam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 sroe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 srcs /irq12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 srwe/we . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 xtal1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 xtal2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 pin description: network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 aui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 di+, di ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 twisted pair interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 rxd+, rxd ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 txd+, txd ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 txp+, txp ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 pin description: ieee 1149.1 (jtag) test access port . . . . . . . . . . . . . . . . . . . . . . . . . . .31 tck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 tdi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 tdo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 tms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 pin description: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 avdd1 ? 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
6 am79c961a avss1 ? 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 dvdd1 ? 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 dvss1 ? 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 connection diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 tqfp 144 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 pin designations: bus master mode (tqfp 144) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 listed by pin number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 pin designations: bus master mode (tqfp 144) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 listed by pin name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 pin designations: bus slave (pio and shared memory) modes (tqfp 144) . . . . . . .35 listed by pin number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 pin designations: bus slave (pio and shared memory) modes (tqfp 144) . . . . . . .36 listed by pin name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 block diagram: pcmcia mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 pin designations: pcmcia mode (tqfp 144) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 listed by pin number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 pin designations: pcmcia mode (tqfp 144) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 listed by pin name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 pin description: pcmcia mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 pcmcia vs. isa pinout comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 pcmcia pin specification changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 1 pcmcia mode block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 pcmcia operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 serial eeprom support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 flash memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 flash memory programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 shared memory vs. programmed i/o implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 flash memory map and card registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 important note about the eeprom byte map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 system interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 bus slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 system interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 plug and play . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 auto-configuration ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 address port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 write_data port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 read_data port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 initiation key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 isolation protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 hardware protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 software protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 plug and play card control registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 plug and play registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 plug and play logical device configuration registers . . . . . . . . . . . . . . . . . . . . .54 detailed functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 eeprom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 important note about the eeprom byte map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 basic eeprom byte map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 amd device driver compatible eeprom byte map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 plug and play register map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 pcnet ? isa ii ? s legacy bit feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 plug & play register locations detailed description (refer to the plug & play register map above) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
am79c961a 7 vendor defined byte (pnp 0xf0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 checksum failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 use without eeprom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 external scan chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 flash prom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 optional ieee address prom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 eisa configuration registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 bus interface unit (biu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 dma transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 1. initialization block dma transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 3 2. descriptor dma transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 3. fifo dma transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 buffer management unit (bmu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 reinitialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 buffer management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 descriptor rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 descriptor ring access mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 transmit descriptor table entry (tdte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 receive descriptor table entry (rdte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 media access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 transmit and receive message data encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 media access management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 2 manchester encoder/decoder (mendec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 external crystal characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 external clock drive characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 5 mendec transmit path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 transmitter timing and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 receive path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 input signal conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 clock acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 pll tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 carrier tracking and end of message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 data decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 differential input terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 collision detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 jitter tolerance definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 attachment unit interface (aui) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 twisted pair transceiver (t-mau) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 twisted pair transmit function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 twisted pair receive function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 link test function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 polarity detection and reversal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 twisted pair interface status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 collision detect function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 signal quality error (sqe) test (heartbeat) function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 jabber function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 power down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 full duplex operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 eadi (external address detection interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 general purpose serial interface (gpsi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 boundary scan circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 tap fsm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 supported instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
8 am79c961a instruction register and decoding logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 boundary scan register (bsr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 other data registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 power saving modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 access operations (software) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 i/o resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 i/o register access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 ieee address access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 boot prom access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 static ram access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 bus cycles (hardware) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 address prom cycles external prom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 address prom cycles using eeprom data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 ethernet controller register cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 5 transmit operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 transmit function programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 automatic pad generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 transmit fcs generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 transmit exception conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 receive operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 receive function programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 automatic pad stripping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 receive fcs checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 receive exception conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 loopback operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 leds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 magic packet operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 magic packet mode activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 magic packet receive indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 5 pcnet-isa ii controller registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 register access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 rap: register address port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 control and status registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 csr0: pcnet-isa ii controller status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 csr1: iadr[15:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 csr2: iadr[23:16] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 csr3: interrupt masks and deferral control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 csr4: test and features control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 csr5: control 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 csr6: rcv/xmt descriptor table length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 csr8: logical address filter, ladrf[15:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 csr9: logical address filter, ladrf[31:16] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 csr10: logical address filter, ladrf[47:32] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 csr11: logical address filter, ladrf[63:48] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 csr12: physical address register, padr[15:0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 csr13: physical address register, padr[31:16] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 csr14: physical address register, padr[47:32] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 csr15: mode register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 csr16: initialization block address lower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 csr17: initialization block address upper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 csr18-19: current receive buffer address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 csr20-21: current transmit buffer address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 csr22-23: next receive buffer address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr24-25: base address of receive ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr26-27: next receive descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr28-29: current receive descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr30-31: base address of transmit ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
am79c961a 9 csr32-33: next transmit descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr34-35: current transmit descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr36-37: next next receive descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr38-39: next next transmit descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr40-41: current receive status and byte count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 csr42-43: current transmit status and byte count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 csr44-45: next receive status and byte count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 csr46: poll time counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 csr47: polling interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 csr48-49: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 csr50-51: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 csr52-53: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr54-55: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr56-57: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr58-59: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr60-61: previous transmit descriptor address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr62-63: previous transmit status and byte count . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr64-65: next transmit buffer address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr66-67: next transmit status and byte count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 csr70-71: temporary storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr72: receive ring counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr74: transmit ring counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr76: receive ring length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr78: transmit ring length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr80: burst and fifo threshold control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 csr82: bus activity timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 csr84-85: dma address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 1 csr86: buffer byte counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 11 csr88-89: chip id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 csr92: ring length conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 csr94: transmit time domain reflectometry count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 csr96-97: bus interface scratch register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr98-99: bus interface scratch register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr104-105: swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr108-109: buffer management scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr112: missed frame count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr114: receive collision count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 csr124: buffer management unit test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 isacsr0: master mode read active/sram data port . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 isacsr1: master mode write active/sram address pointer . . . . . . . . . . . . . . . . . . . . . . . .114 isacsr2: miscellaneous configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 isacsr3: eeprom configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116 isacsr4: led0 status (link integrity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117 isacsr5: led1 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117 isacsr6: led2 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 isacsr7: led3 status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 isacsr8: software configuration register (read-only register) . . . . . . . . . . . . . . . . . . . . .120 isacsr9: miscellaneous configuration 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 initialization block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 rlen and tlen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120 rdra and tdra . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 ladrf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 padr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 receive descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 rmd0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 rmd1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 rmd2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
10 am79c961a rmd3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 transmit descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 tmd0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 tmd1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 tmd2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 tmd3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 register summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 ethernet controller registers (accessed via rdp port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 register summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 register summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 isacsr ? isa bus configuration registers (accessed via idp port) . . . . . . . . . . . . . . . . . .128 system application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 isa bus interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 compatibility considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 bus master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 optional address prom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 32 boot prom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 static ram interface (for shared memory only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 aui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 eeprom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 10base-t interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 operating ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 commercial (c) devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 industrial (i) devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134 switching characteristics: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 switching characteristics: bus master mode ? flash read cycle . . . . . . . . . . 140 switching characteristics: bus master mode ? flash write cycle . . . . . . . . . .140 switching characteristics: shared memory mode . . . . . . . . . . . . . . . . . . . . . . . . . 141 switching characteristics: shared memory mode ? flash read cycle . . . . . .144 switching characteristics: shared memory mode ? flash write cycle . . . . . .144 switching characteristics: eadi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 switching characteristics: jtag (ieee 1149.1) interface . . . . . . . . . . . . . . . . . . . . .145 switching characteristics: gpsi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 switching characteristics: aui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 switching characteristics: 10base-t interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 switching characteristics: serial eeprom interface . . . . . . . . . . . . . . . . . . . . . .148 switching test circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 switching waveforms: bus master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 switching waveforms: shared memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 switching waveforms: gpsi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 2 switching waveforms: eadi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 switching waveforms: jtag (ieee 1149.1) interface . . . . . . . . . . . . . . . . . . . . . . . . . . .173 switching waveforms: aui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 74 switching waveforms: 10base-t interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 physical dimensions* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 pqb132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 physical dimensions* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181 pqb132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181 pcnet-isa ii compatible media interface modules . . . . . . . . . . . . . . . . . . . . . . . . . .183 pcnet-isa ii compatible 10base-t filters and transformers . . . . . . . . . . . . . . . . .183 pcnet-isa ii compatible aui isolation transformers . . . . . . . . . . . . . . . . . . . . . . . . .183 pcnet-isa ii compatible dc/dc converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184 manufacturer contact information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184
am79c961a 11 layout recommendations for reducing noise . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 decoupling low-pass r/c filter design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 digital decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 analog decoupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 avss1 and avdd3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 avss2 and avdd2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 avss2 and avdd2/avdd4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186 sample plug and play configuration record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 sample configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 alternative method for initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189 introduction of the look-ahead packet processing (lapp) concept . . . . . . . . . .191 outline of the lapp flow: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191 setup: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 flow: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 lapp enable software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 lapp enable rules for parsing of descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 some examples of lapp descriptor interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195 buffer size tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 some characteristics of the xxc56 serial eeproms . . . . . . . . . . . . . . . . . . . . . . .201 switching characteristics of a typical xxc56 serial eeprom interface . . . .201 instruction set for the xxc56 series of eeproms . . . . . . . . . . . . . . . . . . . . . . . . . . .202 am79c961a pcnet-isa ii silicon errata report . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 am79c961a rev fd silicon status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
12 am79c961a ordering information standard products amd standard products are available in several packages and operating ranges. the order number (valid combination) is formed by a combination of: valid combinations valid combinations list configurations planned to be sup- ported in volume for this device. consult the local amd sales office to confirm availability of specific valid combinations and to check on newly released combinations. am79c961a k c \w alternate packaging option \w=trimmed and formed (pqb132) optional processing blank=standard processing temperature range c=commercial (0 c to +70 c) i =industrial ( ? 40 c to +85 c) package type (per prod. nomenclature/16-038) k=132-pin plastic quad flat pack (pqr132) v=144-pin thin quad flat package (pqt144) speed not applicable device number/description am79c961a pcnet-isa ii jumperless single-chip ethernet controller for isa valid combinations am79c961a kc, kc\w vc, vc\w am79c961a ki, ki\w vi, vi\w
am79c961a 13 connection diagrams: bus master mode pqfp 132 19364b-2 132 1 dvdd2 tck 131 tms 130 tdo 129 tdi 128 eecs 127 bpcs 126 shfbusy 125 prdb0/eesk 124 prdb1/eedi 123 prdb2/eedo 122 prdb3 121 dvss2 120 prdb4 119 prdb5 118 prdb6 117 prdb7 116 dvdd1 115 led0 114 led1 113 dvss1 112 led2 111 led3 110 dxcvr/ ear 109 av dd2 108 ci+ 107 ci 106 di+ 105 di 104 av dd1 103 do+ 102 do 101 av ss1 100 xtal299 av ss298 xtal197 av dd396 txd+95 txpd+94 txd93 txpd92 av dd491 rxd+90 rxd89 dvss1388 sd1587 sd786 sd1485 sd684 dvss983 sd1382 sd581 sd1280 sd479 dvdd778 sd1177 sd376 sd1075 sd274 dvss873 sd972 sd171 sd870 sd069 sleep 68 dvdd667 34 dvdd4 35 sa12 36 sa13 37 sa14 38 sa15 39 sa16 40 sa17 41 sa18 42 sa19 43 aen 44 iochrdy 45 memw 46 memr 47 dvss11 48 irq15/ apcs 49 irq12/ flashwe 50 irq11 51 dvdd5 52 irq10 53 iocs16 54 bale 55 irq3 56 irq4 57 irq5 58 59 dvs s12 60 drq3 61 dack3 62 ior 63 iow 64 irq9 65 reset 66 dvss3 2 master 3drq7 4drq6 5drq5 6dvss10 7 dack7 8 dack6 9 dack5 10la17 11la18 12la19 13la20 14dvss4 15la21 16la22 17la23 18 sbhe 19dvdd3 20sa0 21sa1 22sa2 23dvss5 24sa3 25sa4 26sa5 27sa6 28sa7 29sa8 30sa9 31dvss6 32sa10 33sa11 am79c961akc ref dvss7
14 am79c961a pin designations: bus master mode listed by pin number pin no. pin name pin no. pin name pin no. pin name pin no. pin name 1 dvss3 34 dvdd4 67 dvdd6 100 avss1 2 master 35 sa12 68 sleep 101 do ? 3 drq7 36 sa13 69 sd0 102 do+ 4 drq6 37 sa14 70 sd8 103 avdd1 5 drq5 38 sa15 71 sd1 104 di ? 6 dvss10 39 dvss7 72 sd9 105 di+ 7dack7 40 sa16 73 dvss8 106 ci ? 8dack6 41 sa17 74 sd2 107 ci+ 9dack5 42 sa18 75 sd10 108 avdd2 10 la17 43 sa19 76 sd3 109 dxcvr/ear 11 la18 44 aen 77 sd11 110 led3 12 la19 45 iochrdy 78 dvdd7 111 led2 13 la20 46 memw 79 sd4 112 dvss1 14 dvss4 47 memr 80 sd12 113 led1 15 la21 48 dvss11 81 sd5 114 led0 16 la22 49 irq15/apcs 82 sd13 115 dvdd1 17 la23 50 irq12/flashwe 83 dvss9 116 prdb7 18 sbhe 51 irq11 84 sd6 117 prdb6 19 dvdd3 52 dvdd5 85 sd14 118 prdb5 20 sa0 53 irq10 86 sd7 119 prdb4 21 sa1 54 iocs16 87 sd15 120 dvss2 22 sa2 55 bale 88 dvss13 121 prdb3 23 dvss5 56 irq3 89 rxd ? 122 prdb2/eedo 24 sa3 57 irq4 90 rxd+ 123 prdb1/eedi 25 sa4 58 irq5 91 avdd4 124 prdb0/eesk 26 sa5 59 ref 92 txpd ? 125 shfbusy 27 sa6 60 dvss12 93 txd ? 126 bpcs 28 sa7 61 drq3 94 txpd+ 127 eecs 29 sa8 62 dack3 95 txd+ 128 tdi 30 sa9 63 ior 96 avdd3 129 tdo 31 dvss6 64 iow 97 xtal1 130 tms 32 sa10 65 irq9 98 avss2 131 tck 33 sa11 66 reset 99 xtal2 132 dvdd2
am79c961a 15 pin designations: bus master mode listed by pin name pin name pin no. pin name pin no. pin name pin no. pin name pin no. aen 44 dvss12 60 led2 111 sa6 27 avdd1 103 dvss13 88 led3 110 sa7 28 avdd2 108 dvss2 120 master 2 sa8 29 avdd3 96 dvss3 1 memr 47 sa9 30 avdd4 91 dvss4 14 memw 46 sbhe 18 avss1 100 dvss5 23 prdb0/eesk 124 sd0 69 avss2 98 dvss6 31 prdb1/eedi 123 sd1 71 bale 55 dvss7 39 prdb2/eedo 122 sd10 75 bpcs 126 dvss8 73 prdb3 121 sd11 77 ci ? 106 dvss9 83 prdb4 119 sd12 80 ci+ 107 dxcvr/ear 109 prdb5 118 sd13 82 dack3 62 eecs 127 prdb6 117 sd14 85 dack5 9 iochrdy 45 prdb7 116 sd15 87 dack6 8iocs16 54 ref 59 sd2 74 dack7 7ior 63 reset 66 sd3 76 di ? 104 iow 64 rxd ? 89 sd4 79 di+ 105 irq10 53 rxd+ 90 sd5 81 do ? 101 irq11 51 sa0 20 sd6 84 do+ 102 irq12/flashwe 50 sa1 21 sd7 86 drq3 61 irq15/apcs 49 sa10 32 sd8 70 drq5 5 irq3 56 sa11 33 sd9 72 drq6 4 irq4 57 sa12 35 shfbusy 125 drq7 3 irq5 58 sa13 36 sleep 68 dvdd1 115 irq9 65 sa14 37 tck 131 dvdd2 132 la17 10 sa15 38 tdi 128 dvdd3 19 la18 11 sa16 40 tdo 129 dvdd4 34 la19 12 sa17 41 tms 130 dvdd5 52 la20 13 sa18 42 txd ? 93 dvdd6 67 la21 15 sa19 43 txd+ 95 dvdd7 78 la22 16 sa2 22 txpd ? 92 dvss1 112 la23 17 sa3 24 txpd+ 94 dvss10 6 led0 114 sa4 25 xtal1 97 dvss11 48 led1 113 sa5 26 xtal2 99
16 am79c961a pin designations: bus master mode listed by group pin name pin function i/o driver isa bus interface aen bale dack [3, 5 ? 7] drq[3, 5 ? 7] iochrdy iocs16 ior iow irq[3, 4, 5, 9, 10, 11, 12, 15] la[17-23] master memr memw ref reset sa[0 ? 19] sbhe sd[0 ? 15] address enable bus address latch enable dma acknowledge dma request i/o channel ready i/o chip select 16 i/o read select i/o write select interrupt request unlatched address bus master transfer in progress memory read select memory write select memory refresh active system reset system address bus system byte high enable system data bus i i i i/o i/o o i i o i/o o o o i i i/o i/o i/o ts3 od3 od3 ts3/od3 ts3 od3 ts3 ts3 ts3 ts3 ts3 board interfaces irq15/apcs bpcs dxcvr/ear led0 led1 led2 led3 prdb[3 ? 7] sleep xtal1 xtal2 shfbusy prdb(0)/eesk prdb(1)/eedi prdb(2)/eedo eecs irq15 or address prom chip select boot prom chip select disable transceiver led0/lnkst led1 /sfbd/rcvact led2 /srd/rxdatpol led3 /srdclk/xmtact prom data bus sleep mode crystal input crystal output read access from eeprom in process serial shift clock serial shift data in serial shift data out eeprom chip select o o i/o o o o o i/o i i o i/o i/o i/o o ts1 ts1 ts1 ts2 ts2 ts2 ts2 ts1
am79c961a 17 pin designations: bus master mode (continued) listed by group output driver types pin name pin function i/o driver attachment unit interface (aui) ci di do collision inputs receive data tr a n s m i t d a t a i i o twisted pair transceiver interface (10base-t) rxd txd txpd 10base-t receive data 10base-t transmit data 10base-t predistortion control i o o ieee 1149.1 test access port interface (jtag) tck tdi tdo tms test clock test data input test data output test mode select i i o i ts2 power supplies avdd avss dvdd dvss analog power [1-4] analog ground [1-2] digital power [1-7] digital ground [1-13] name type iol (ma) ioh (ma) pf ts1 tri-state 4 ? 150 ts2 tri-state 12 ? 450 ts3 tri-state 24 ? 3120 od3 open drain 24 ? 3120
18 am79c961a pin description: bus master mode these pins are part of the bus master mode. in order to understand the pin descriptions, definition of some terms from a draft of ieee p996 are included. ieee p996 terminology alternate master : any device that can take control of the bus through assertion of the master signal. it has the ability to generate addresses and bus control sig- nals in order to perform bus operations. all alternate masters must be 16 bit devices and drive sbhe . bus ownership : the current master possesses bus ownership and can assert any bus control, address and data lines. current master : the permanent master, temporary master or alternate master which currently has owner- ship of the bus. permanent master : each p996 bus will have a device known as the permanent master that provides certain signals and bus control functions as described in sec- tion 3.5 (of the ieee p996 spec.), ? permanent master ? . the permanent master function can reside on a bus adapter or on the backplane itself. temporary master : a device that is capable of gener- ating a dma request to obtain control of the bus and directly asserting only the memory and i/o strobes during bus transfer. addresses are generated by the dma device on the permanent master. isa interface aen address enable input this signal must be driven low when the bus performs an i/o access to the device. bale used to latch the la20 ? 23 address lines. dack 3, 5-7 dma acknowledge input asserted low when the permanent master acknowl- edges a dma request. when dack is asserted the pcnet-isa ii controller becomes the current master by asserting the master signal. drq 3, 5-7 dma request input/output when the pcnet-isa ii controller needs to perform a dma transfer, it asserts drq. the permanent master acknowledges drq with the assertion of dack . when the pcnet-isa ii does not need the bus it desserts drq. the pcnet-isa ii provides for fair bus bandwidth sharing between two bus mastering devices on the isa bus through an adaptive delay which is inserted between back-to-back dma requests. see the back-to-back dma requests section for details. because of the operation of the plug and play regis- ters, the dma channels on the pcnet-isa ii must be attached to the specific drq and dack signals on the pc/at bus as indicated by the pin names. iochrdy i/o channel ready input/output when the pcnet-isa ii controller is being accessed, iochrdy high indicates that valid data exists on the data bus for reads and that data has been latched for writes. when the pcnet-isa ii controller is the current master on the isa bus, it extends the bus cycle as long as iochrdy is low. iocs16 i/o chip select 16 output when an i/o read or write operation is performed, the pcnet-isa ii controller will drive the iocs16 pin low to indicate that the chip supports a 16-bit operation at this address. (if the motherboard does not receive this signal, then the motherboard will convert a 16-bit access to two 8-bit accesses). the pcnet-isa ii controller follows the ieee p996 spec- ification that recommends this function be implemented as a pure decode of sa0-9 and aen, with no depen- dency on ior , or iow ; however, some pc/at clone sys- tems are not compatible with this approach. for this reason, the pcnet-isa ii controller is recommended to be configured to run 8-bit i/o on all machines. since data is moved by memory cycles there is virtually no perfor- mance loss incurred by running 8-bit i/o and compatibil- ity problems are virtually eliminated. the pcnet-isa ii controller can be configured to run 8-bit-only i/o by clearing bit 0 in plug and play register f0. ior i/o read input ior is driven low by the host to indicate that an input/ output read operation is taking place. ior is only valid if the aen signal is low and the external address matches the pcnet-isa ii controller ? s predefined i/o address location. if valid, ior indicates that a slave read operation is to be performed. iow i/o write input iow is driven low by the host to indicate that an input/ output write operation is taking place. iow is only valid if aen signal is low and the external address matches the pcnet-isa ii controller ? s predefined i/o address location. if valid, iow indicates that a slave write oper- ation is to be performed.
am79c961a 19 irq 3, 4, 5, 9, 10, 11, 12, 15 interrupt request output an attention signal which indicates that one or more of the following status flags is set: babl, miss, merr, rint, idon, rcvcco, jab, mpco, or txdatstrt. all status flags have a mask bit which allows for sup- pression of irq assertion. these flags have the following meaning: because of the operation of the plug and play regis- ters, the interrupts on the pcnet-isa ii must be attached to specific irq signals on the pc/at bus. la17-23 unlatched address bus input/output the unlatched address bus is driven by the pcnet-isa ii controller during bus master cycle. the functions of these unlatched address pins will change when gpsi mode is invoked. the following table shows the pin configuration in gpsi mode. please refer to the section on general purpose serial interface for detailed information on accessing this mode. master master mode input/output this signal indicates that the pcnet-isa ii controller has become the current master of the isa bus. after the pcnet-isa ii controller has received a dma acknowledge (dack ) in response to a dma request (drq), the ethernet controller asserts the master signal to indicate to the permanent master that the pc- net-isa ii controller is becoming the current master. memr memory read input/output memr goes low to perform a memory read operation. memw memory write input/output memw goes low to perform a memory write operation. ref memory refresh input when ref is asserted, a memory refresh is active. the pcnet-isa ii controller uses this signal to mask inad- vertent dma acknowledge assertion during memory refresh periods. if dack is asserted when ref is active, dack assertion is ignored. ref is monitored to eliminate a bus arbitration problem observed on some isa platforms. reset reset input when reset is asserted high the pcnet-isa ii con- troller performs an internal system reset. reset must be held for a minimum of 10 xtal1 periods before being deasserted. while in a reset state, the pcnet-isa ii controller will tristate or deassert all outputs to pre- defined reset levels. the pcnet-isa ii controller resets itself upon power-up. sa0-19 system address bus input/output this bus contains address information, which is stable during a bus operation, regardless of the source. sa17-19 contain the same values as the unlatched address la17-19. when the pcnet-isa ii controller is the current master, sa0-19 will be driven actively. when the pcnet-isa ii controller is not the current master, the sa0-19 lines are continuously monitored to determine if an address match exists for i/o slave transfers or boot prom accesses. sbhe system byte high enable input/output this signal indicates the high byte of the system data bus is to be used. sbhe is driven by the pcnet-isa ii controller when performing bus mastering operations. sd0-15 system data bus input/output these pins are used to transfer data to and from the pcnet-isa ii controller to system resources via the isa data bus. sd0-15 is driven by the pcnet-isa ii control- babl babble rcvcco receive collision count overflow jab jabber miss missed frame merr memory error mpco missed packet count overflow rint receive interrupt idon initialization done txdatstrt transmit start pin number pin function in bus master mode pin function in gpsi mode 10 la17 rxdat 11 la18 srdclk 12 la19 rxcrs 13 la20 clsn 15 la21 stdclk 16 la22 txen 17 la23 txdat
20 am79c961a ler when performing bus master writes and slave read operations. likewise, the data on sd0-15 is latched by the pcnet-isa ii controller when performing bus master reads and slave write operations. board interface irq12/flashwe flash write enable output optional interface to the flash memory boot prom write enable. irq15/apcs address prom chip select output when programmed as apcs in plug and play register f0, this signal is asserted when the external address prom is read. when an i/o read operation is performed on the first 16 bytes in the pcnet-isa ii con- troller ? s i/o space, apcs is asserted. the outputs of the external address prom drive the prom data bus. the pcnet-isa ii controller buffers the contents of the prom data bus and drives them on the lower eight bits of the system data bus. when programmed to irq15 (default), this pin has the same function as irq 3, 4, 5, 9, 10, 11, or 12. bpcs boot prom chip select output this signal is asserted when the boot prom is read. if sa0-19 lines match a predefined address block and memr is active and ref inactive, the bpcs signal will be asserted. the outputs of the external boot prom drive the prom data bus. the pcnet-isa ii controller buffers the contents of the prom data bus and drives them on the lower eight bits of the system data bus. dxcvr/ear disable transceiver/ external address reject input/output this pin can be used to disable external transceiver circuitry attached to the aui interface when the internal 10base-t port is active. the polarity of this pin is set by the dxcvrp bit (pnp register 0xf0, bit 5). when dxcvrp is cleared (default), the dxcvr pin is driven high when the twisted pair port is active or sleep mode has been entered and driven low when the aui port is active. when dxcvrp is set, the dxcvr pin is driven low when the twisted pair port is active or sleep mode has been entered and driven high when the aui port is active. if eadi mode is selected, this pin becomes the ear input. the incoming frame will be checked against the inter- nally active address detection mechanisms and the result of this check will be or ? d with the value on the ear pin. the ear pin is defined as reject . (see the eadi section for details regarding the function and timing of this signal). ledo-3 led drivers output these pins sink 12 ma each for driving leds. their meaning is software configurable (see section the isa bus configuration registers ) and they are active low. when eadi mode is selected, the pins named led1 , led2 , and led3 change in function while led0 continues to indicate 10base-t link status. prdb3-7 private data bus input/output this is the data bus for the boot prom and the address prom. prdb2/eedo private data bus bit 2/data out input/output a multifunction pin which serves as prdb2 of the private data bus and, when isacsr3 bit 4 is set, changes to become data out from the eeprom. prdb1/eedi private data bus bit 1/data in input/output a multifunction pin which serves as prdb1 of the private data bus and, when isacsr3 bit 4 is set, changes to become data in to the eeprom. prdb0/eesk private data bus bit 0/ serial clock input/output a multifunction pin which serves as prdb0 of the private data bus and, when isacsr3 bit 4 is set, changes to become serial clock to the eeprom. led eadi function 1sf/bd 2srd 3 srdclk
am79c961a 21 shfbusy shift busy input/output this pin indicates that a read from the external eeprom is in progress. it is active only when data is being shifted out of the eeprom due to a hardware reset or assertion of the ee_load bit (isacsr3, bit 14). if this pin is left unconnected or pulled low with a pull-down resistor, an eeprom checksum error is forced. normally, this pin should be connected to v cc through a 10k ? pull-up resistor. eecs eeprom chip select output this signal is asserted when read or write accesses are being performed to the eeprom. it is controlled by isacsr3. it is driven at reset during eeprom read. sleep sleep input when sleep pin is asserted (active low), the pc- net-isa ii controller performs an internal system reset and proceeds into a power savings mode. all outputs will be placed in their normal reset condition. all pc- net-isa ii controller inputs will be ignored except for the sleep pin itself. deassertion of sleep results in the device waking up. the system must delay the starting of the network controller by 0.5 seconds to allow inter- nal analog circuits to stabilize. xtal1 crystal connection input the internal clock generator uses a 20 mhz crystal that is attached to pins xtal1 and xtal2. alternatively, an external 20 mhz cmos-compatible clock signal can be used to drive this pin. refer to the section on external crystal characteristics for more details. xtal2 crystal connection output the internal clock generator uses a 20 mhz crystal that is attached to pins xtal1 and xtal2. if an external clock is used, this pin should be left unconnected.
22 am79c961a connection diagrams: bus slave mode pqfp 132 132 1 dvdd2 tck 131 tms 130 tdo 129 tdi 128 eecs 127 bpcs 126 shfbusy 125 prdb0/eesk 124 prdb1/eedi 123 prdb2/eedo 122 prdb3 121 dvss2 120 prdb4 119 prdb5 118 prdb6 117 prdb7 116 dvdd1 115 led0 114 led1 113 dvss1 112 led2 111 led3 110 dxcvr/ear 109 avdd2 108 ci+ 107 ci ? 106 di+ 105 di ? 104 avdd1 103 do+ 102 do ? 101 avss1 100 xtal2 99 avss2 98 xtal1 97 avdd3 96 txd+ 95 txpd+ 94 txd ? 93 txpd ? 92 avdd4 91 rxd+ 90 rxd ? 89 dvss13 88 sd15 87 sd7 86 sd14 85 sd6 84 dvss9 83 sd13 82 sd5 81 sd12 80 sd4 79 dvdd7 78 sd11 77 sd3 76 sd10 75 sd2 74 dvss8 73 sd9 72 sd1 71 sd8 70 sd0 69 sleep 68 dvdd6 67 34 dvdd4 35 prab12 36 prab13 37 prab14 38 prab15 39 sa13 40 sa14 41 sa15 42 srwe 43 aen 44 iochrdy 45 memw 46 memr 47 dvss11 48 apcs/irq15 49 srcs/irq12 50 irq11 51 dvdd5 52 irq10 53 iocs16 54 bpam 55 irq3 56 irq4 57 irq5 58 59 dvss12 60 sroe 61 smam 62 ior 63 iow 64 irq9 65 reset 66 dvss3 2 sma 3 sa0 4 sa1 5 sa2 6 dvss10 7 sa3 8 sa4 9 sa5 10 sa6 11 sa7 12 sa8 13 sa9 14 dvss4 15 sa10 16 sa11 17 sa12 18 sbhe 19 dvdd3 20 prab0 21 prab1 22 prab2 23 dvss5 24 prab3 25 prab4 26 prab5 27 prab6 28 prab7 29 prab8 30 prab9 31 dvss6 32 prab10 33 prab11 am79c961akc ref dvss7 19364b-3
am79c961a 23 block diagram: bus slave mode 19364b-4 led [0-3] isa bus interface unit rcv fifo xmt fifo fifo control buffer management unit eeprom interface unit 802.3 mac core encoder/ decoder (pls) & aui port 10base-t mau private bus control jtag port control aen iochrdy ior iow irq[3, 4, 5, 9, 10, 11, 12] iocs16 memr memw ref reset sbhe sd[0-15] sa[0-15] sleep shfbusy eedo eedi eesk eecs dxcvr/ear ci+/- di+/- xtal1 xtal2 do+/- rxd+/- txd+/- txpd+/- tdo tms tdi tck sma irq15/apcs bpcs prab[0-15] prdb[0-7] sroe srwe smam bpam dvdd[1-7] dvss[1-13] avdd[1-4] avss[1-2]
24 am79c961a pin designations: bus slave mode listed by pin number pin # name pin # name pin # name 1 dvss3 sma sa0 sa1 sa2 dvss10 sa3 sa4 sa5 sa6 sa7 sa8 45 iochrdy 89 rxd- rxd+ avdd4 txpd- txd- txpd+ txd+ avdd3 xtal1 avss2 xtal2 avss1 do- do+ avdd1 di- di+ ci- ci+ avdd2 dxcvr/ear led3 led2 dvss1 led1 led0 246memw 90 347memr 91 4 48 dvss11 92 5 49 irq15 93 6 50 irq12 94 7 51 irq11 95 8 52 dvdd5 96 9 53 irq10 97 10 54 iocs16 98 11 55 bpam 99 12 56 irq3 100 13 sa9 dvss4 sa10 sa11 sa12 sbhe dvdd3 prab0 prab1 prab2 dvss5 prab3 prab4 prab5 prab6 prab7 prab8 prab9 dvss6 prab10 prab11 dvdd4 prab12 prab13 57 irq4 101 14 58 irq5 102 15 59 ref 103 16 60 dvss12 104 17 61 sroe 105 18 62 smam 106 19 63 ior 107 20 64 iow 108 21 65 irq9 109 22 66 reset 110 23 67 dvdd6 111 24 68 sleep 112 25 69 sd0 113 26 70 sd8 114 27 71 sd1 115 dvdd1 prdb7 prdb6 prdb5 prdb4 dvss2 prdb3 prdb2/eedo prdb1/eedi prdb0/eesk shfbusy bpcs eecs tdi tdo tms tck dvdd2 28 72 sd9 116 29 73 dvss8 117 30 74 sd2 118 31 75 sd10 119 32 76 sd3 120 33 77 sd11 121 34 78 dvdd7 122 35 79 sd4 123 36 80 sd12 124 37 prab14 prab15 dvss7 sa13 sa14 sa15 srwe aen 81 sd5 125 38 82 sd13 126 39 83 dvss9 127 40 84 sd6 128 41 85 sd14 129 42 86 sd7 130 43 87 sd15 131 44 88 dvss13 132
am79c961a 25 pin designations: bus slave mode listed by pin name name pin# name pin# name pin# aen avdd1 avdd2 avdd3 avdd4 avss1 avss2 bpam bpcs ci- ci+ di- di+ do- do+ dvdd1 dvdd2 dvdd3 dvdd4 dvdd5 dvdd6 dvdd7 dvss1 dvss10 dvss11 dvss12 44 irq15 49 sa13 sa14 sa15 sa2 sa3 sa4 sa5 sa6 sa7 sa8 sa9 sbhe sd0 sd1 sd10 sd11 sd12 sd13 sd14 sd15 sd2 sd3 sd4 40 103 irq3 56 41 108 irq4 57 42 96 irq5 58 5 91 irq9 65 7 100 led0 114 8 98 led1 113 9 55 led2 111 10 126 led3 110 11 106 memr 47 12 107 memw 46 13 104 prab0 20 18 105 prab1 21 69 101 prab10 32 71 102 prab11 33 75 115 prab12 35 77 132 prab13 36 80 19 prab14 37 82 34 prab15 38 85 52 prab2 22 87 67 prab3 24 74 78 prab4 25 76 112 prab5 26 79 6 prab6 27 sd5 sd6 sd7 sd8 sd9 shfbusy sleep sma smam sroe srwe tck tdi tdo tms txd- txd+ txpd- txpd+ xtal1 xtal2 81 48 prab7 28 84 60 prab8 29 86 dvss13 dvss2 dvss3 dvss4 dvss5 dvss6 dvss7 dvss8 dvss9 dxcvr/ear eecs iochrdy iocs16 ior iow irq10 irq11 irq12 88 prab9 30 70 120 prdb0/do 124 72 1 prdb0/d1 123 125 14 prdb0/sclk 122 68 23 prdb3 121 2 31 prdb4 119 62 39 prdb5 118 61 73 prdb6 117 43 83 prdb7 116 131 109 ref 59 128 127 reset 66 129 45 rxd- 89 130 54 rxd+ 90 93 63 sa0 3 95 64 sa1 4 92 53 sa10 15 94 51 sa11 16 97 50 sa12 17 99
26 am79c961a pin designations: bus slave mode listed by group pin name pin function i/o driver isa bus interface aen address enable i iochrdy i/o channel ready o od3 iocs16 i/o chip select 16 o od3 ior i/o read select i iow i/o write select i irq[3, 4, 5, 9, 10, 11, 12, 15] interrupt request o ts3/od3 memr memory read select i memw memory write select i ref memory refresh active i reset system reset i sa[0 ? 15] system address bus i sbhe system byte high enable i sd[0 ? 15] system data bus i/o ts3 board interfaces irq15/apcs irq15 or address prom chip select o ts1 bpcs boot prom chip select o ts1 bpam boot prom address match i dxcvr/ear disable transceiver i/o ts1 led0 led0 /lnkst ots2 led1 led1 /sfbd/rcvact ots2 led2 led2 /srd/rxdatd01 ots2 led3 led3 /srdclk/xmtact ots2 prab[0 ? 15] private address bus i/o ts3 prdb[3 ? 7] private data bus i/o ts1 sleep sleep mode i sma slave mode architecture i smam shared memory address match i sroe static ram output enable o ts3 srwe static ram write enable o ts1 xtal1 crystal oscillator input i xtal2 crystal oscillator output o shfbusy read access from eeprom in process o prdb(0)/eesk serial shift clock i/o prdb(1)/eedi serial shift data in i/o prdb(2)/eedo serial shift data out i/o eecs eeprom chip select o
am79c961a 27 pin designations: bus slave mode listed by group output driver types pin name pin function i/o driver attachment unit interface (aui) ci di do collision inputs receive data tr a n s m i t d a t a i i o twisted pair transceiver interface (10base-t) rxd txd txpd 10base-t receive data 10base-t transmit data 10base-t predistortion control i o o ieee 1149.1 test access port interface (jtag) tck tdi tdo tms test clock test data input test data output test mode select i i o i ts2 power supplies avdd avss dvdd dvss analog power [1-4] analog ground [1-2] digital power [1-7] digital ground [1-13] name type i ol (ma) i oh (ma) pf ts1 tri-state 4 ? 150 ts2 tri-state 12 ? 450 ts3 tri-state 24 ? 3120 od3 open drain 24 ? 3120
28 am79c961a pin description: bus slave mode isa interface aen address enable input this signal must be driven low when the bus performs an i/o access to the device. iochrdy i/o channel ready output when the pcnet-isa ii controller is being accessed, a high on iochrdy indicates that valid data exists on the data bus for reads and that data has been latched for writes. iocs16 i/o chip select 16 input/output when an i/o read or write operation is performed, the pcnet-isa ii controller will drive this pin low to indi- cate that the chip supports a 16-bit operation at this address. (if the motherboard does not receive this signal, then the motherboard will convert a 16-bit access to two 8-bit accesses). the pcnet-isa ii controller follows the ieee p996 spec- ification that recommends this function be implemented as a pure decode of sa0-9 and aen, with no depen- dency on ior , or iow ; however, some pc/at clone systems are not compatible with this approach. for this reason, the pcnet-isa ii controller is recommended to be configured to run 8-bit i/o on all machines. since data is moved by memory cycles there is virtually no performance loss incurred by running 8-bit i/o and compatibility problems are virtually eliminated. the pc- net-isa ii controller can be configured to run 8-bit-only i/ o by clearing bit 0 in plug and play register f0. ior i/o read input to perform an input/output read operation on the device ior must be asserted. ior is only valid if the aen signal is low and the external address matches the pcnet-isa ii controller ? s predefined i/o address location. if valid, ior indicates that a slave read opera- tion is to be performed. iow i/o write input to perform an input/output write operation on the device iow must be asserted. iow is only valid if aen signal is low and the external address matches the pcnet-isa ii controller ? s predefined i/o address loca- tion. if valid, iow indicates that a slave write operation is to be performed. irq3, 4, 5, 9, 10, 11, 12, 15 interrupt request output an attention signal which indicates that one or more of the following status flags is set: babl, miss, merr, rint, idon or txstrt. all status flags have a mask bit which allows for suppression of irq assertion. these flags have the following meaning: memr memory read input memr goes low to perform a memory read operation. memw memory write input memw goes low to perform a memory write opera- tion. ref memory refresh input when ref is asserted, a memory refresh cycle is in progress. during a refresh cycle, memr assertion is ignored. reset reset input when reset is asserted high, the pcnet-isa ii controller performs an internal system reset. reset must be held for a minimum of 10 xtal1 periods before being deasserted. while in a reset state, the pcnet-isa ii controller will tristate or deassert all outputs to predefined reset levels. the pcnet-isa ii controller resets itself upon power-up. sa0-15 system address bus input this bus carries the address inputs from the system address bus. address data is stable during command active cycle. babl babble rcvcco receive collision count overflow jab jabber miss missed frame merr memory error mpco missed packet count overflow rint receive interrupt idon initialization done txstrt transmit start
am79c961a 29 sbhe system bus high enable input this signal indicates the high byte of the system data bus is to be used. there is a weak pull-up resistor on this pin. if the pcnet-isa ii controller is installed in an 8-bit only system like the pc/xt, sbhe will always be high and the pcnet-isa ii controller will perform only 8-bit operations. there must be at least one low going edge on this signal before the pcnet-isa ii controller will perform 16-bit operations. sd0-15 system data bus input/output this bus is used to transfer data to and from the pc- net-isa ii controller to system resources via the isa data bus. sd0-15 is driven by the pcnet-isa ii controller when performing slave read operations. likewise, the data on sd0-15 is latched by the pc- net-isa ii controller when performing slave write operations. board interface apcs /irq15 address prom chip select output this signal is asserted when the external address prom is read. when an i/o read operation is per- formed on the first 16 bytes in the pcnet-isa ii controller ? s i/o space, apcs is asserted. the outputs of the external address prom drive the prom data bus. the pcnet-isa ii controller buffers the contents of the prom data bus and drives them on the lower eight bits of the system data bus. iocs16 is not asserted during this cycle. bpam boot prom address match input this pin indicates a boot prom access cycle. if no boot prom is installed, this pin has a default value of high and thus may be left connected to v dd . bpcs boot prom chip select output this signal is asserted when the boot prom is read. if bpam is active and memr is active, the bpcs signal will be asserted. the outputs of the external boot prom drive the prom data bus. the pcnet-isa ii controller buffers the contents of the prom data bus and drives them on the system data bus. iocs16 is not asserted during this cycle. if 16-bit cycles are performed, it is the responsibility of external logic to assert memcs16 signal. dxcvr/ear disable transceiver/ external address reject input/output this pin disables the transceiver. the dxcvr output is configured in the initialization sequence. a high level indicates the twisted pair interface is active and the aui is inactive, or sleep mode has been entered. a low level indicates the aui is active and the twisted pair interface is inactive. if eadi mode is selected, this pin becomes the ear input. the incoming frame will be checked against the inter- nally active address detection mechanisms and the result of this check will be or ? d with the value on the ear pin. the ear pin is defined as reject . (see the eadi section for details regarding the function and tim- ing of this signal). led0-3 led drivers output these pins sink 12 ma each for driving leds. their meaning is software configurable (see section the isa bus configuration registers ) and they are active low. when eadi mode is selected, the pins named led1 , led2 , and led3 change in function while led0 continues to indicate 10base-t link status. the dxcvr input becomes the ear input. prab0-15 private address bus input/output the private address bus is the address bus used to drive the address prom, remote boot prom, and sram. prdb3-7 private data bus input/output this is the data bus for the static ram, the boot prom, and the address prom. prdb2/eedo private data bus bit 2/data out input/output a multifunction pin which serves as prdb2 of the private data bus and, when isacsr3 bit 4 is set, changes to become data out from the eeprom. led eadi function 1sf/bd 2srd 3 srdclk
30 am79c961a prdb1/eedi private data bus bit 1/data in input/output a multifunction pin which serves as prdb1 of the private data bus and, when isacsr3 bit 4 is set, changes to become data in to the eeprom. prdb0/eesk private data bus bit 0/ serial clock input/output a multifunction pin which serves as prdb0 of the private data bus and, when isacsr3 bit 4 is set, changes to become serial clock to the eeprom. shfbusy shift busy input/output this pin indicates that a read from the external eeprom is in progress. it is active only when data is being shifted out of the eeprom due to a hardware reset or assertion of the ee_load bit (isacsr3, bit 14). if this pin is left unconnected or pulled low with a pull-down resistor, an eeprom checksum error is forced. normally, this pin should be connected to v cc through a 10k ? pull-up resistor. eecs eeprom chip select output this signal is asserted when read or write accesses are being performed to the eeprom. it is controlled by isacsr3. it is driven at reset during eeprom read. sleep sleep input when sleep input is asserted (active low), the pc- net-isa ii controller performs an internal system reset and proceeds into a power savings mode. all outputs will be placed in their normal reset condition. all pc- net-isa ii controller inputs will be ignored except for the sleep pin itself. deassertion of sleep results in the device waking up. the system must delay the starting of the network controller by 0.5 seconds to allow inter- nal analog circuits to stabilize. sma slave mode architecture input this pin must be permanently pulled low for operation in the bus slave mode. it is sampled after the hardware reset sequence. in the bus slave mode, the pc- net-isa ii can be programmed for shared memory ac- cess or programmed i/o access through the piosel bit (isacsr2, bit 13). smam shared memory address match input when the shared memory architecture is selected (isacsr2, bit 13), this pin is an input that indicates an access to shared memory when asserted. the type of access is decided by memr or memw . when the programmed i/o architecture is selected, this pin should be permanently tied high. sroe static ram output enable output this pin directly controls the external sram ? s oe pin. srcs /irq12 static ram chip select output this pin directly controls the external sram ? s chip select (cs ) pin when the flash boot rom option is selected. when flash boot rom option is not selected, this pin becomes irq12. srwe/we static ram write enable/ write enable output this pin (srwe ) directly controls the external sram ? s we pin when a flash memory device is not implemented. when a flash memory device is implemented, this pin becomes a global write enable (we ) pin. xtal1 crystal connection input the internal clock generator uses a 20 mhz crystal that is attached to pins xtal1 and xtal2. alternatively, an external 20 mhz cmos-compatible clock signal can be used to drive this pin. refer to the section on external crystal characteristics for more details. xtal2 crystal connection output the internal clock generator uses a 20 mhz crystal that is attached to pins xtal1 and xtal2. if an external clock is used, this pin should be left unconnected.
am79c961a 31 pin description: network interfaces aui ci+, ci ? control input input this is a differential input pair used to detect collision (signal quality error signal). di+, di ? data in input this is a differential receive data input pair to the pc- net-isa ii controller. do+, do ? data out output this is a differential transmit data output pair from the pcnet-isa ii controller. twisted pair interface rxd+, rxd ? receive data input this is the 10base-t port differential receive input pair. txd+, txd ? transmit data output these are the 10base-t port differential transmit drivers. txp+, txp ? transmit predistortion control output these are 10base-t transmit waveform pre-distortion control differential outputs. pin description: ieee 1149.1 (jtag) test access port tck test clock input this is the clock input for the boundary scan test mode operation. tck can operate up to 10 mhz. tck does not have an internal pull-up resistor and must be con- nected to a valid ttl level of high or low. tck must not be left unconnected. tdi test data input input this is the test data input path to the pcnet-isa ii con- troller. if left unconnected, this pin has a default value of high. tdo test data output output this is the test data output path from the pcnet-isa ii controller. tdo is tri-stated when jtag port is inactive. tms test mode select input this is a serial input bit stream used to define the spe- cific boundary scan test to be executed. if left uncon- nected, this pin has a default value of high. pin description: power supplies all power pins with a ? d ? prefix are digital pins con- nected to the digital circuitry and digital i/o buffers. all power pins with an ? a ? prefix are analog power pins connected to the analog circuitry. not all analog pins are quiet and special precaution must be taken when doing board layout. some analog pins are more noisy than others and must be separated from the other analog pins. avdd1 ? 4 analog power (4 pins) power supplies power to analog portions of the pcnet-isa ii controller. special attention should be paid to the printed circuit board layout to avoid excessive noise on these lines. avss1 ? 2 analog ground (2 pins) power supplies ground reference to analog portions of pc- net-isa ii controller. special attention should be paid to the printed circuit board layout to avoid excessive noise on these lines. dvdd1 ? 7 digital power (7 pins) power supplies power to digital portions of pcnet-isa ii con- troller. four pins are used by input/output buffer drivers and two are used by the internal digital circuitry. dvss1 ? 13 digital ground (13 pins) power supplies ground reference to digital portions of pc- net-isa ii controller. ten pins are used by input/output buffer drivers and two are used by the internal digital circuitry.
32 am79c961a connection diagram 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 am79c961avc tqfp 144 19364b-5
am79c961a 33 pin designations: bus master mode (tqfp 144) listed by pin number pin no. pin name pin no. pin name pin no. pin name pin no. pin name 1 nc 37 nc 73 nc 109 nc 2 dvss3 38 dvdd4 74 dvdd6 110 avss1 3 master 39 sa12 75 sleep 111 do ? 4 drq7 40 sa13 76 sd0 112 do+ 5 drq6 41 sa14 77 sd8 113 avdd1 6 drq5 42 sa15 78 sd1 114 di ? 7 dvss10 43 dvss7 79 sd9 115 di+ 8dack7 44 sa16 80 dvss8 116 ci ? 9dack6 45 sa17 81 sd2 117 ci+ 10 dack5 46 sa18 82 sd10 118 avdd2 11 la17 47 sa19 83 sd3 119 dxcvr/ear 12 la18 48 aen 84 sd11 120 led3 13 la19 49 iochrdy 85 dvdd7 121 led2 14 la20 50 memw 86 sd4 122 dvss1 15 dvss4 51 memr 87 sd12 123 led1 16 la21 52 dvss11 88 sd5 124 led0 17 la22 53 irq15/apcs 89 sd13 125 dvdd1 18 la23 54 irq12/flashwe 90 dvss9 126 prdb7 19 sbhe 55 irq11 91 sd6 127 prdb6 20 dvdd3 56 dvdd5 92 sd14 128 prdb5 21 sa0 57 irq10 93 sd7 129 prdb4 22 sa1 58 iocs16 94 sd15 130 dvss2 23 sa2 59 bale 95 dvss13 131 prdb3 24 dvss5 60 irq3 96 rxd ? 132 prdb2/eedo 25 sa3 61 irq4 97 rxd+ 133 prdb1/eedi 26 sa4 62 irq5 98 avdd4 134 prdb0/eesk 27 sa5 63 ref 99 txpd ? 135 shfbusy 28 sa6 64 dvss12 100 txd ? 136 bpcs 29 sa7 65 drq3 101 txpd+ 137 eecs 30 sa8 66 dack3 102 txd+ 138 tdi 31 sa9 67 ior 103 avdd3 139 tdo 32 dvss6 68 iow 104 xtal1 140 tms 33 sa10 69 irq9 105 avss2 141 tck 34 sa11 70 reset 106 xtal2 142 dvdd2 35 nc 71 nc 107 nc 143 nc 36 nc 72 nc 108 nc 144 nc
34 am79c961a pin designations: bus master mode (tqfp 144) listed by pin name pin name pin no. pin name pin no. pin name pin no. pin name pin no. aen 48 dvss3 2 nc 37 sa3 25 avdd1 113 dvss4 15 nc 71 sa4 26 avdd2 118 dvss5 24 nc 72 sa5 27 avdd3 103 dvss6 32 nc 73 sa6 28 avdd4 98 dvss7 43 nc 107 sa7 29 avss1 110 dvss8 80 nc 108 sa8 30 avss2 105 dvss9 90 nc 109 sa9 31 bale 59 dxcvr/ear 119 nc 143 sbhe 19 bpcs 136 eecs 137 nc 144 sd0 76 ci+ 117 iochrdy 49 prdb0/eesk 134 sd1 78 ci ? 116 iocs16 58 prdb1/eedi 133 sd10 82 dack3 66 ior 67 prdb2/eedo 132 sd11 84 dack5 10 iow 68 prdb3 131 sd12 87 dack6 9 irq10 57 prdb4 129 sd13 89 dack7 8 irq11 55 prdb5 128 sd14 92 di+ 115 irq12/flashwe 54 prdb6 127 sd15 94 di ? 114 irq15/apcs 53 prdb7 126 sd2 81 do+ 112 irq3 60 ref 63 sd3 83 do ? 111 irq4 61 reset 70 sd4 86 drq3 65 irq5 62 rxd+ 97 sd5 88 drq5 6 irq9 69 rxd ? 96 sd6 91 drq6 5 la17 11 sa0 21 sd7 93 drq7 4 la18 12 sa1 22 sd8 77 dvdd1 125 la19 13 sa10 33 sd9 79 dvdd2 142 la20 14 sa11 34 shfbusy 135 dvdd3 20 la21 16 sa12 39 sleep 75 dvdd4 38 led0 124 sa13 40 tck 141 dvdd5 56 led1 123 sa14 41 tdi 138 dvdd6 74 led2 121 sa15 42 tdo 139 dvdd7 85 led3 120 sa16 44 tms 140 dvss1 122 master 3 sa17 45 txd+ 102 dvss10 7 memr 51 sa18 46 txd ? 100 dvss11 52 memw 50 sa19 47 txpd+ 101 dvss12 64 nc 1 sa2 23 txpd ? 99 dvss13 95 nc 35 sa22 17 xtal1 104 dvss2 130 nc 36 sa23 18 xtal2 106
am79c961a 35 pin designations: bus slave (pio and shared memory) modes (tqfp 144) listed by pin number pin no. pin name pin no. pin name pin no. pin name pin no. pin name 1nc37 nc 73nc109nc 2 dvss3 38 dvdd4 74 dvdd6 110 avss1 3sma 39 prab12 75 sleep 111 do- 4 sa0 40 prab13 76 sd0 112 do+ 5 sa1 41 prab14 77 sd8 113 avdd1 6 sa2 42 prab15 78 sd1 114 di- 7 dvss10 43 dvss7 79 sd9 115 di+ 8 sa3 44 sa13 80 dvss8 116 ci- 9 sa4 45 sa14 81 sd2 117 ci+ 10 sa5 46 sa15 82 sd10 118 avdd2 11 sa6 47 srwe 83 sd3 119 dxcvr/ear 12 sa7 48 aen 84 sd11 120 led3 13 sa8 49 iochrdy 85 dvdd7 121 led2 14 sa9 50 memw 86 sd4 122 dvss1 15 dvss4 51 memr 87 sd12 123 led1 16 sa10 52 dvss11 88 sd5 124 led0 17 sa11 53 irq15 89 sd13 125 dvdd1 18 sa12 54 irq12 90 dvss9 126 prdb7 19 sbhe 55 irq11 91 sd6 127 prdb6 20 dvdd3 56 dvdd5 92 sd14 128 prdb5 21 prab0 57 irq10 93 sd7 129 prdb4 22 prab1 58 iocs16 94 sd15 130 dvss2 23 prab2 59 bpam 95 dvss13 131 prdb3 24 dvss5 60 irq3 96 rxd- 132 prdb2/ eedo 25 prab3 61 irq4 97 rxd+ 133 prdb1/eedi 26 prab4 62 irq5 98 avdd4 134 prdb0/eesk 27 prab5 63 ref 99 txpd- 135 shfbusy 28 prab6 64 dvss12 100 txd- 136 bpcs 29 prab7 65 sroe 101 txpd+ 137 eecs 30 prab8 66 smam 102 txd+ 138 tdi 31 prab9 67 ior 103 avdd3 139 tdo 32 dvss6 68 iow 104 xtal1 140 tms 33 prab10 69 irq9 105 avss2 141 tck 34 prab11 70 reset 106 xtal2 142 dvdd2 35 nc 71 pcmcia_mode 107 nc 143 nc 36 nc 72 nc 108 nc 144 nc
36 am79c961a pin designations: bus slave (pio and shared memory) modes (tqfp 144) listed by pin name pin name pin no. pin name pin no. pin name pin no. pin name pin no. aen 48 eecs 137 prab13 40 sa7 12 avdd1 113 iochrdy 49 prab14 41 sa8 13 avdd2 118 iocs16 58 prab15 42 sa9 14 avdd3 103 ior 67 prab2 23 sbhe 19 avdd4 98 iow 68 prab3 25 sd0 76 avss1 110 irq10 57 prab4 26 sd1 78 avss2 105 irq11 55 prab5 27 sd10 82 bpam 59 irq12 54 prab6 28 sd11 84 bpcs 136 irq15 53 prab7 29 sd12 87 ci+ 117 irq3 60 prab8 30 sd13 89 ci ? 116 irq4 61 prab9 31 sd14 92 di+ 115 irq5 62 prdb0/eesk 134 sd15 94 di ? 114 irq9 69 prdb1/eedi 133 sd2 81 do+ 112 led0 124 prdb2/eedo 132 sd3 83 do ? 111 led1 123 prdb3 131 sd4 86 dvdd1 125 led2 121 prdb4 129 sd5 88 dvdd2 142 led3 120 prdb5 128 sd6 91 dvdd3 20 memr 51 prdb6 127 sd7 93 dvdd4 38 memw 50 prdb7 126 sd8 77 dvdd5 56 nc 1 ref 63 sd9 79 dvdd6 74 nc 35 reset 70 shfbusy 135 dvdd7 85 nc 36 rxd+ 97 sleep 75 dvss1 122 nc 37 rxd ? 96 smam 66 dvss10 7 nc 72 sa0 4 sma 3 dvss11 52 nc 73 sa1 5 sroe 65 dvss12 64 nc 107 sa10 16 srwe 47 dvss13 95 nc 108 sa11 17 tck 141 dvss2 130 nc 109 sa12 18 tdi 138 dvss3 2 nc 143 sa13 44 tdo 139 dvss4 15 nc 144 sa14 45 tms 140 dvss5 24 pcmcia_mode 71 sa15 46 txd+ 102 dvss6 32 prab0 21 sa2 6 txd ? 100 dvss7 43 prab1 22 sa3 8 txpd+ 101 dvss8 80 prab10 33 sa4 9 txpd ? 99 dvss9 90 prab11 34 sa5 10 xtal1 104 dxcvr/ ear 119 prab12 39 sa6 11 xtal2 106
am79c961a 37 block diagram: pcmcia mode 19364b-6 pcmcia bus interface unit rcv fifo xmt fifo fifo control buffer management unit eeprom interface unit 802.3 mac core encoder/ decoder (pls) & aui port 10base-t mau private bus control jtag port control reg ce2 ce1 wait inpack stschg iord iowr ireq iois16 oe we v cc reset a[0-15] d[0-15] pcmcia_mode sma smam shfbusy eedo eedi eesk dvdd[1-7] dvss[1-13] avdd[1-4] avss[1-2] dxcvr/ear ci di xtal1 xtal2 do rxd txd txpd flcs led [0-3] prab[0-15] prdb[0 ? 7] tdo tms tdi tck sleep eecs sroe srwe srcs optional
38 am79c961a pin designations: pcmcia mode (tqfp 144) listed by pin number pin no. pin name pin no. pin name pin no. pin name pin no. pin name 1 nc 37 nc 73 nc 109 nc 2 dvss3 38 dvdd4 74 dvdd6 110 avss1 3sma 39 prab12 75 sleep 111 do ? 4 sa0 40 prab13 76 sd0 112 do+ 5 sa1 41 prab14 77 sd8 113 avdd1 6 sa2 42 prab15 78 sd1 114 di ? 7 dvss10 43 dvss7 79 sd9 115 di+ 8 sa3 44 sa13 80 dvss8 116 ci ? 9 sa4 45 sa14 81 sd2 117 ci+ 10 sa5 46 sa15 82 sd10 118 avdd2 11 sa6 47 srwe 83 sd3 119 dxcvr/ear 12 sa7 48 reg 84 sd11 120 led3 13 sa8 49 wait 85 dvdd7 121 led2 14 sa9 50 we 86 sd4 122 dvss1 15 dvss4 51 oe 87 sd12 123 led1 16 sa10 52 dvss11 88 sd5 124 led0 17 sa11 53 nc 89 sd13 125 dvdd1 18 sa12 54 srcs 90 dvss9 126 prdb7 19 ce2 55 inpack 91 sd6 127 prdb6 20 dvdd3 56 dvdd5 92 sd14 128 prdb5 21 prab0 57 stschg 93 sd7 129 prdb4 22 prab1 58 iois16 94 sd15 130 dvss2 23 prab2 59 ce1 95 dvss13 131 prdb3 24 dvss5 60 ireq 96 rxd ? 132 prdb2/eedo 25 prab3 61 nc 97 rxd+ 133 prdb1/eedi 26 prab4 62 nc 98 avdd4 134 prdb0/eesk 27 prab5 63 ref 99 txpd ? 135 shfbusy 28 prab6 64 dvss12 100 txd ? 136 flcs 29 prab7 65 sroe 101 txpd+ 137 eecs 30 prab8 66 smam 102 txd+ 138 tdi 31 prab9 67 iord 103 avdd3 139 tdo 32 dvss6 68 iowr 104 xtal1 140 tms 33 prab10 69 nc 105 avss2 141 tck 34 prab11 70 reset 106 xtal2 142 dvdd2 35 nc 71 pcmcia_mode 107 nc 143 nc 36 nc 72 nc 108 nc 144 nc
am79c961a 39 pin designations: pcmcia mode (tqfp 144) listed by pin name pin name pin no. pin name pin no. pin name pin no. pin name pin no. avdd1 113 inpack 55 prab4 26 sd1 78 avdd2 118 iois16 58 prab5 27 sd10 82 avdd3 103 iord 67 prab6 28 sd11 84 avdd4 98 iowr 68 prab7 29 sd12 87 avss1 110 ireq 60 prab8 30 sd13 89 avss2 105 led0 124 prab9 31 sd14 92 ce1 59 led1 123 prdb0/eesk 134 sd15 94 ce2 19 led2 121 prdb1/eedi 133 sd2 81 ci+ 117 led3 120 prdb2/eedo 132 sd3 83 ci ? 116 nc 1 prdb3 131 sd4 86 di+ 115 nc 35 prdb4 129 sd5 88 di ? 114 nc 36 prdb5 128 sd6 91 do+ 112 nc 37 prdb6 127 sd7 93 do ? 111 nc 53 prdb7 126 sd8 77 dvdd1 125 nc 61 ref 63 sd9 79 dvdd2 142 nc 62 reg 48 shfbusy 135 dvdd3 20 nc 69 reset 70 sleep 75 dvdd4 38 nc 72 rxd+ 97 smam 64 dvdd5 56 nc 73 rxd ? 96 smam 66 dvdd6 74 nc 107 sa0 4 srcs 54 dvdd7 85 nc 108 sa1 5 sroe 65 dvss1 122 nc 109 sa10 16 srwe 47 dvss10 7 nc 143 sa11 17 stschg 57 dvss11 52 nc 144 sa12 18 tck 141 dvss13 95 oe 51 sa13 44 tdi 138 dvss2 130 pcmcia_mode 71 sa14 45 tdo 139 dvss3 2 prab0 21 sa15 46 tms 140 dvss4 15 prab1 22 sa2 6 txd+ 102 dvss5 24 prab10 33 sa3 8 txd ? 100 dvss6 32 prab11 34 sa4 9 txpd+ 101 dvss7 43 prab12 39 sa5 10 txpd ? 99 dvss8 80 prab13 40 sa6 11 vss 3 dvss9 90 prab14 41 sa7 12 wait 49 dxcvr/ear 119 prab15 42 sa8 13 we 50 eecs 137 prab2 23 sa9 14 xtal1 104 flcs 136 prab3 25 sd0 76 xtal2 106
40 am79c961a pin description: pcmcia mode the pcmcia pins function as described in the pcmcia specification revision 2.1. please refer to it for more details. the non-pcmcia pins used by the 144-pin tqfp package have the same functions as described by ? pin description: bus slave mode ? for isa operation begin- ning on page 26 of the am79c961a pcnet-isa ii data sheet (pid #19364a) with the exception of pin 71, pcmcia_mode. pcmcia_mode input sets the device for pcmcia operation when tied high. this pin is not available in the 132-pin pqfp package option.
am79c961a 41 pcmcia vs. isa pinout comparison the pins listed below are pin definition changes spe- cific to pcmcia mode: in pcmcia mode, a number of the input pins have internal resistors turned on with a resistance greater than 100 k ? . these resistors are ei- ther connected to v cc or v ss . the diagram below shows the pin connections for the isa slave mode and pcmcia mode. pcmcia pin specification changes in isa mode, the iochrdy and iocs16 signals are defined as open drain outputs. in pcmcia mode, the wait and i ois16 signals are full cmos drivers. in pcmcia mode, the max values for t ior8 , t mr8 and t sfr10 change from 10 ns to ? 40 ns. ? pcmcia-mode 1 should be tied to v ss in isa slave mode ? pcmcia-mode 2 should be tied to v cc in pcmcia mode ? sleep 3 pin remains functional in pcmcia mode, it is recommended to tie it to v cc pin number tqfp144 isa slave mode pcmcia mode pcmcia input pin resistance > 100 k ? 19 sbhe ce2 to v cc 48 aen reg to v cc 49 iochrdy wait 50 memw we to v cc 51 memr oe to v cc 53 irq15 nc 54 irq12 srcs 55 irq11 inpack 57 irq10 stschg 58 iocs16 iois16 59 bpam ce1 to v cc 60 irq3 ireq 61 irq4 nc 62 irq5 nc 67 ior iord to v cc 68 iow iowr to v cc 69 irq9 nc 70 reset reset to v cc 71 pcmcia_mode 1 pcmcia_mode 2 75 sleep sleep 3 sd0 ? sd15 d0 ? d15 to gnd sa0 ? sa15 a0 ? a15 to gnd
42 am79c961a pcmcia mode block diagram pcnet-isa ii controller prab[0 ? 15] srcs srwe smam sd[0 ? 15] sa[0 ? 15] prdb[0 ? 7] sroe flcs pcmcia bus 16-bit system data system address bus d[0 ? 7] a[1 ? 19] note: smam shown only for shared memory architecture designs. smam should be tied high on the pcnet-isa ii for programmed i/o architecture designs in order to access the flash memory at common memory location zero. sram 70 ns we cs oe a[0 ? 15] we cs oe flash/eprom 120 ns 19364b-7 pcmcia control a[0] d[0 ? 7] (upper address pin) [0] plug and play compatible with flash memory support
am79c961a 43 functional description pcmcia operation when a pcmcia card is first plugged into a pcmcia host, all pcmcia cards respond as a memory only device. in the pcmcia standard there are two memory spaces, common memory and attribute memory. the reg pin determines which memory space is selected. after the host detects that the pcmcia card is inserted, the host reads a section of the attribute memory called the cis (card information structure) which provides configuration information about the inserted card. the attribute memory is a byte wide memory which is only addressable on even bytes. consequently, odd byte accesses are not defined for attribute memory. mapped in the cis area are four card configuration registers which are physically located inside the pcnet-isa ii device. in the pcnet-isa ii device there are four registers which are located at decimal byte address 1008, 1010, 1012 and 1014, respectively. inside the cis data structure, there is information which provides the base address of the card configuration registers. inside first card configuration register is a configura- tion index region which allows programming the device to support i/o accesses. the pcnet-isa ii supports pcmcia ? s independent i/o address window mecha- nism. when i/o enable is set in the ccr 0 register the pcnet-isa ii controller will respond to i/o commands. the lower 5 address bits decode register accesses. the pcmcia host is expected to decode i/o address bits 6 and above and only assert ce1 and/or ce2 if the upper i/o address lines match. after the host has mapped the pcmcia ? s card resources to the system, the card should be visible by the system and the driver may be loaded. serial eeprom support the serial eeprom is not required in pcmcia mode but can be used to hold the contents of the ieee address eeprom. for cost purposes, it is recommended to place the ieee address in the cis (card information structure) attribute memory. flash memory map the pcnet-isa ii device supports either a single flash or eprom device. the external flash device contains the cis area as well as an area located in common memory used to hold software drivers. the attribute memory ori- gin is located at byte 0. the common memory region is accessed when reg is deasserted and an access to common memory occurs. smam is normally connected to an upper address line on the pcmcia card. when a high order address is asserted the flash memory will be selected. accesses to common memory when smam is low will access the shared ram when shared memory mode is selected. if programmed i/o mode is used, the smam can be tied high which will result in the flash ? s base address being mapped to location zero. flash memory programming the flash memory device can be read at anytime. in order to program the flash device, the apwen bit must be set in isacsr2 register to allow write operations to the flash or non-volatile eeprom device. shared memory vs. programmed i/o implications the pcnet-isa ii controller in pcmcia modes allows for the local packet buffer memory to be mapped into com- mon memory or indirectly accessed through i/o ac- cesses. if shared memory is chosen, the local sram will be mapped as a memory resource. consequently, the cis will have to indicate this requirement to the system. if programmed i/o is used no additional memory re- sources will be required to be allocated by the system.
44 am79c961a flash memory map and card registers ccr 3 ccr 1 ccr 2 ccr 0 reserved cis data flash common memory (not available) (unused) 131070 byte (1fffeh) 1024 byte (400h) 1022 byte (3feh) 1016 byte (3f8h) 1014 byte (3f6h) 1012 byte (3f4h) 1010 byte (3f2h) 1008 byte (3f0h) 1006 byte (3eeh) 0 byte (0h) attribute memory common memory 19364b-8
am79c961a 45 functional description the pcnet-isa ii controller is a highly integrated system solution for the pc-at isa architecture. it provides a full duplex ethernet controller, aui port, and 10base-t transceiver. the pcnet-isa ii controller can be directly in- terfaced to an isa system bus. the pcnet-isa ii control- ler contains an isa bus interface unit, dma buffer management unit, 802.3 media access control function, separate 136-byte transmit and 128-byte receive fifos, ieee defined attachment unit interface (aui), and twisted-pair transceiver media attachment unit. in addi- tion, a sleep function has been incorporated which pro- vides low standby current for power sensitive applications. the pcnet-isa ii controller is register compatible with the lance (am7990) ethernet controller and pc- net-isa (am79c960). the dma buffer management unit supports the lance descriptor software model and the pcnet-isa ii controller is software compatible with the novell ne2100 and ne1500t add-in cards. external remote boot proms and ethernet physical address proms are supported. the location of the i/o registers, ethernet address prom, and the boot prom are determined by the programming of the registers in- ternal to pcnet-isa ii. these registers are loaded at reset from the eeprom, if an eeprom is utilized. normally, the ethernet physical address will be stored in the eeprom with the other configuration data. this reduces the parts count, board space requirements, and power consumption. the option to use a standard parallel 8 bit prom is provided to manufactures who are concerned about the non-volatile nature of eeproms. the pcnet-isa ii controller ? s bus master architecture brings to system manufacturers (adapter card and motherboard makers alike) something they have not been able to enjoy with other architectures ? a low-cost system solution that provides the lowest parts count and highest performance. as a bus-mastering device, costly and power-hungry external srams are not needed for packet buffering. this results in lower sys- tem cost due to fewer components, less real-estate and less power. the pcnet-isa ii controller ? s advanced bus mastering architecture also provides high data through- put and low cpu utilization for even better performance. to offer greater flexibility, the pcnet-isa ii controller has a bus slave mode to meet varying application needs. the bus slave mode utilizes a local sram memory to store the descriptors and buffers that are located in sys- tem memory when in bus master mode. the sram can be slave accessed on the isa bus through memory cycles in shared memory mode or i/o cycles in pro- grammed i/o mode. the shared memory and pro- grammed i/o architectures offer maximum compatibility with low-end machines, such as pc/xts that do not support bus mastering, and very high end machines which require local packet buffering for increased system latency. the network interface provides an attachment unit interface and twisted-pair transceiver functions. only one interface is active at any particular time. the aui allows for connection via isolation transformer to 10base5 and 10base2, thick and thin based coaxial cables. the twisted-pair transceiver interface allows for connection of unshielded twisted-pair cables as specified by the section 14 supplement to ieee 802.3 standard (type 10base-t). important note about the eeprom byte map the user is cautioned that while the am79c961a (pc- net-isa ii) and its associated eeprom are pin compatible to their predecessors the am79c961 (pcnet-isa + ) and its associated eeprom, the byte map structure in each of the eeproms are different from each other. the eeprom byte map structure used for the am79c961a pcnet-isa ii has the addition of ? misc con- fig 2, isacsr9" at word location 10hex. the eeprom byte map structure used for the am79c961 pcnet-isa+ does not have this. therefore, should the user intend to replace the pc- net-isa + with the pcnet-isa ii, care must be taken to re- program the eeprom to reflect the new byte map structure needed and used by the pcnet-isa ii. for addi- tional information, refer to the section in this data sheet under eeprom and the am79c961 pcnet-isa + data sheet (pid #18183) under the sections entitled eeprom and serial eeprom byte map . bus master mode system interface the pcnet-isa ii controller has two fundamental oper- ating modes, bus master and bus slave. within the bus slave mode, the pcnet-isa ii can be programmed for a shared memory or programmed i/o architecture. the selection of either the bus master mode or the bus slave mode must be done through hard wiring; it is not software configurable. when in the bus slave mode, the selection of the shared memory or programmed i/o architecture is done through software with the piosel bit (isacsr2, bit 13). the optional boot prom is in memory address space and is expected to be 8 ? 64k. on-chip address compar- ators control device selection is based on the value in the eeprom. the address prom, board configuration registers, and the ethernet controller occupy 24 bytes of i/o space and can be located at 16 different starting addresses.
46 am79c961a 19364b-9 eecs isa bus 16-bit system data 24-bit system address pcnet-isa ii controller boot prom (optional) sd[0-15] sa[0-19] la[17-23] bpcs ce oe d[0-7] a[0-15] do di sk cs org eeprom (optional, common) v cc shfbusy v cc prdb[2]/eedo prdb[1]/eedi prdb[0]/eesk prdb[0-7] bus master block diagram plug and play compatible 19364b-10 bus master block diagram plug and play compatible we isa bus 24-bit system address pcnet-isa ii controller ieee address prom (optional) sd[0-15] sa[0-19] la[17-23] prdb[0-7] d[0-7] bpcs a[0-4] sk di do cs oe eeprom (optional, common) eecs flash (optional) prdb[0]/eesk prdb[1]/eedi prdb[2]/eedo g cs org d[0-7] a[0-15] 16-bit system data shfbusy v cc irq15/apcs irq12/flashwe with flash and parallel address prom support v cc
am79c961a 47 bus slave mode system interface the bus slave mode is the other fundamental operat- ing mode available on the pcnet-isa ii controller. within the bus slave mode, the pcnet-isa ii can be programmed for a shared memory or programmed i/o architecture. in the bus slave mode the pcnet-isa ii controller uses the same descriptor and buffer architec- ture as in the bus master mode, but these data struc- tures are stored in a static ram controlled by the pcnet-isa ii controller. when operating with the shared memory architecture, the local sram is visible as a memory resource on the pc which can be accessed through memory cycles on the isa bus inter- face. when operating with the programmed i/o archi- tecture, the local sram is accessible through i/o cycles on the isa bus. specifically, the sram is acces- sible using the rap and idp i/o ports to access the isacsr0 and isacsr1 registers, which serve as the sram data port and sram address pointer port, respectively. in the bus slave mode, the pcnet-isa ii registers and optional ethernet physical address prom look the same and are accessed in the same way as in the bus master mode. the boot prom is selected by an external device which drives the boot prom address match (bpam ) input to the pcnet-isa ii controller. the pcnet-isa ii controller can perform two 8-bit accesses from the 8-bit boot prom and present 16-bits of data to accommo- date 16 bit read accesses on the isa bus. when using the shared memory architecture mode, access to the local sram works the same way as access to the boot prom, with an external device gen- erating the shared memory address match (smam ) signal and the pcnet-isa ii controller performing the sram read or write and the 8/16 bit data conversion. external logic must also drive memcs16 appropriately for the 128kbyte segment decoded from the la[23:17] signals. the programmed i/o architecture mode uses the rap and idp ports to allow access to the local sram hence, external address decoding is not necessary and the smam pin is not used in programmed i/o architec- ture mode (smam should be tied high in the pro- grammed i/o architecture mode). similar to the shared memory architecture mode, in the programmed i/o ar- chitecture mode, 8/16 bit conversion occurs when 16 bit reads and writes are performed on the sram data port (isacsr1). converting the local sram accesses from 8-bit cycles to 16-bit cycles allows use of the much faster 16-bit cycle timing while cutting the number of bus cycles in half. this raises performance to more than 400% of what could be achieved with 8-bit cycles. when the shared memory architecture mode is used, converting boot prom accesses to 16-bit cycles allows the two memory resources to be in the same 128 kbyte block of memory without a clash between two devices with different data widths. the pcnet-isa ii prefetches data from the sram to allow fast, minimum wait-state read accesses of con- secutive sram addresses. in both the shared memory architecture and the programmed i/o architecture, prefetch data is read from a speculated address that assumes that successive reads in time will be from adjacent ascending addresses in the sram. at the beginning of each sram read cycle, the pcnet-isa ii determines whether the prefetched data can be assumed to be valid. if the prefetched data can be assumed to be valid, it is driven onto the isa bus without inserting any wait states. if the prefetched data cannot be assumed to be valid, the pcnet-isa ii will in- sert wait states into the isa bus read cycle until the correct word is read from the sram.
48 am79c961a bus slave block diagram plug and play compatible with flash memory support eecs isa bus 24-bit system address pcnet-isa ii controller prdb[2]/eedo prdb[1]/eedi prdb[0]/eesk 16-bit system data prab[0-15] irq12/srcs v cc d[0-7] d[0 ? 7] a[0-15] a[0 ? 15] memcs16 sa[16] la[17-23] v cc note: smam shown only for shared memory architecture designs. smam should be tied high on the pcnet-isa ii for programmed i/o architecture designs. srwe smam smam shfbusy bpam sd[0] sa[0] prdb[0] sroe bpcs we cs oe sram external glue logic bpam shfbusy sin clk eeprom we cs oe do di sk cs org flash (optional) 19364b-11
am79c961a 49 plug and play plug and play is a standardized method of configuring jumperless adapter cards in a system. plug and play is a microsoft standard and is based on a central software configuration program, either in the operating system or elsewhere, which is responsible for configuring all plug and play cards in a system. plug and play is fully supported by the pcnet-isa ii ethernet controller. for a copy of the microsoft plug and play specification contact microsoft inc. this specification should be referenced in addition to pcnet-isa ii technical reference manual and this data sheet. operation if the pcnet-isa ii ethernet controller is used to boot off the network, the device will come up active at reset, otherwise it will come up inactive. information stored in the serial eeprom is used to identify the card and to describe the system resources required by the card, such as i/o space, memory space, irqs and dma channels. this information is stored in a standardized read only format. operation of the plug and play system is shown as follows: isolate the plug and play card read the cards resource data identify the card configure its resources the plug and play mode of operation allows the follow- ing benefits to the end user. eliminates all jumpers or dip switches from the adapter card ease of use is greatly enhanced allows the ability to uniquely address identical cards in a system, without conflict allows the software configuration program or os to read out the system resource requirements required by the card defines a mechanism to set or modify the current configuration of each card maintain backward compatibility with other isa bus adapters auto-configuration ports three 8 bit i/o ports are used by the plug and play con- figuration software on each plug and play device to communicate with the plug and play registers. the ports are listed in the table below. the software config- uration space is defined as a set of 8 bit registers. these registers are used by the plug and play software configuration to issue commands, access the resource information, check status, and configure the pcnet-isa ii controller hardware. the address and write_data ports are located at fixed, predefined i/o addresses. the write_data port is located at an alias of the address port. all three auto-configuration ports use a 12-bit isa address decode. the read_data port is relocatable within the range 0x203 ? 0x3ff by a command written to the write_data port. address port the internal plug and play registers are accessed by writing the address to the address port and then either reading the read_data port or writing to the write_data port. once the address port has been written, any number of reads or writes can occur without having to rewrite the address port. the address port is also the address to which the initiation key is written to, which is described later. write_data port the write_data port is the address to which all writes to the internal plug and play registers occur. the destination of the data written to the write_data port is determined by the last value written to the address port. read_data port the read_data port is used to read information from the internal plug and play registers. the register to be read is determined by the last value of the address port. the i/o address of the read_data port is set by writing the chosen i/o location to plug and play reg- ister 0. the isolation protocol can determine that the address chosen is free from conflict with other devices i/o ports. initiation key the pcnet-isa ii controller is disabled at reset when operating in plug and play mode. it will not respond to any memory or i/o accesses, nor will the pcnet-isa ii controller drive any interrupts or dma channels. the initiation key places the pcnet-isa ii device into the configuration mode. this is done by writing a pre- defined pattern to the address port. if the proper sequence of i/o writes are detected by the pcnet-isa ii device, the plug and play auto-configuration ports port name location type address 0x279 (printer status port) write-only write-data 0xa79 (printer status port + 0x0800) write-only read-data relocatable in range 0x0203-0x03ff read-only
50 am79c961a are enabled. this pattern must be sequential, i.e., any other i/o access to this i/o port will reset the state machine which is checking the pattern. interrupts should be disabled during this time to eliminate any extraneous i/o cycles. the exact sequence for the initiation key is listed below in hexadecimal. 6a, b5, da, ed, f6, fb, 7d, be df, 6f, 37, 1b, 0d, 86, c3, 61 b0, 58, 2c, 16, 8b, 45, a2, d1 e8, 74, 3a, 9d, ce, e7, 73, 39 isolation protocol a simple algorithm is used to isolate each plug and play card. this algorithm uses the signals on the isa bus and requires lock-step operation between the plug and play hardware and the isolation software. the key element of this mechanism is that each card contains a unique number, referred to as the serial identifier for the rest of the discussion. the serial iden- tifier is a 72-bit unique, non-zero, number composed of two, 32-bit fields and an 8-bit checksum. the first 32-bit field is a vendor identifier. the other 32 bits can be any value, for example, a serial number, part of a lan address, or a static number, as long as there will never be two cards in a single system with the same 64 bit number. the serial identifier is accessed bit-serially by the isolation logic and is used to differentiate the cards. the shift order for all plug and play serial isolation and resource data is defined as bit[0], bit[1], and so on through bit[7]. hardware protocol the isolation protocol can be invoked by the plug and play software at any time. the initiation key, described earlier, puts all cards into configuration mode. the hardware on each card expects 72 pairs of i/o read accesses to the read_data port. the card ? s response to these reads depends on the value of each bit of the serial identifier which is being examined one bit at a time in the sequence shown above. if the current bit of the serial identifier is a ? 1", then the card will drive the data bus to 0x55 to complete the first i/o read cycle. if the bit is ? 0", then the card puts its data bus driver into high impedance. all cards in high imped- ance will check the data bus during the i/o read cycle to sense if another card is driving d[1:0] to ? 01". during the second i/o read, the card(s) that drove the 0x55, will now drive a 0xaa. all high impedance cards will check the data bus to sense if another card is driving d[1:0] to ? 10". between pairs of reads, the software should wait at least 30 s. if a high impedance card sensed another card driving the data bus with the appropriate data during both cycles, then that card ceases to participate in the cur- rent iteration of card isolation. such cards, which lose out, will participate in future iterations of the isolation protocol. note: during each read cycle, the plug and play hard- ware drives the entire 8-bit databus, but only checks the lower 2 bits. state isolation read all 72 bits from serial identifier id bit = ? 1h ? sd[1:0] = ? 01" wait for next read from serial isolation register sd[1:0] = ? 10" state sleep one card isolated read from serial isolation register get one bit from serial identifier yes no no yes drive ? 55h ? on sd[7:0] leave sd in high-impedance leave sd in high-impedance drive ? aah ? on sd[7:0] no yes no yes after i/o read completes, fetch next id bit from serial identifier id = 0; other card id = 1 19364b-12 plug and play isa card isolation algorithm shifting of serial identifier byte 0 byte 3 byte 2 byte 1 byte 0 byte 3 byte 2 byte 1 byte 0 shift check- sum serial number vendor id 19364b-13
am79c961a 51 if a card was driving the bus or if the card was in high impedance and did not sense another card driving the bus, then it should prepare for the next pair of i/o reads. the card shifts the serial identifier by one bit and uses the shifted bit to decide its response. the above sequence is repeated for the entire 72-bit serial identifier. at the end of this process, one card remains. this card is assigned a handle referred to as the card select number (csn) that will be used later to select the card. cards which have been assigned a csn will not partic- ipate in subsequent iterations of the isolation protocol. cards must be assigned a csn before they will respond to the other commands defined in the specification. it should be noted that the protocol permits the 8-bit checksum to be stored in non-volatile memory on the card or generated by the on-card logic in real-time. the same lfsr algorithm described in the initiation key section of the plug and play specification is used in the checksum generation. software protocol the plug and play software sends the initiation key to all plug and play cards to place them into configuration mode. the software is then ready to perform the isola- tion protocol. the plug and play software generates 72 pairs of l/o read cycles from the read_data port. the software checks the data returned from each pair of i/o reads for the 0x55 and 0xaa driven by the hardware. if both 0x55 and 0xaa are read back, then the software assumes that the hardware had a ? 1" bit in that position. all other results are assumed to be a ? 0. ? during the first 64 bits, software generates a checksum using the received data. the checksum is compared with the checksum read back in the last 8 bits of the sequence. there are two other special considerations for the soft- ware protocol. during an iteration, it is possible that the 0x55 and 0xaa combination is never detected. it is also possible that the checksum does not match if either of these cases occur on the first iteration, it must be assumed that the read_data port is in conflict. if a conflict is detected, then the read_data port is relocated. the above process is repeated until a non- conflicting location for the read_data port is found. the entire range between 0x203 and 0x3ff is avail- able, however in practice it is expected that only a few locations will be tried before software determines that no plug and play cards are present. during subsequent iterations, the occurrence of either of these two special cases should be interpreted as the absence of any further plug and play cards (i.e. the last card was found in the previous iteration). this terminates the isolation protocol. note: the software must delay 1 ms prior to starting the first pair of isolation reads, and must wait 250 sec between each subsequent pair of isolation reads. this delay gives the isa card time to access information from possibly very slow storage devices. plug and play card control registers the state transitions and card control commands for the pcnet-isa ii controller are shown in the following figure.
52 am79c961a plug and play isa card state transitions notes: 1. csn = card select number. 2. reset_drv causes a state transition from the current state to wait for key and sets all csns to zero. all logical devices are set to their power-up configuration values. 3. the wait for key command causes a state transition from the current state to wait for key. power up reset_drv state active commands initiation key set csn = 0 wait for key no active commands state active commands sleep reset wait for key wake[csn] state active commands isolation reset wait for key set rd_data port serial isolation wake[csn] state active commands config reset wait for key wake[csn] resource data status logical device i/o range check activate configuration registers set csn lose serial location or (wake <> csn) wake <> csn 19364b-13 plug and play registers the pcnet-isa ii controller supports all of the defined plug and play card control registers. refer to the tables on the following pages for detailed information.
am79c961a 53 plug and play standard registers name address port value definition set rd_data port 0x00 writing to this location modifies the address of the port used for reading from the plug and play isa cards. bits [7:0] become i/o read port address bits [9:2] . reads from this register are ignored. i/o address bits 11:10 should = 00, and 1:0 = 11. serial isolation 0x01 a read to this register causes a plug and play card in the isolation state to compare one bit of the board ? s id. this process is fully described above. this register is read only. config control 0x02 bit[0] - reset all logical devices and restore configuration registers to their power-up values. bit[1] - return to the wait for key state bit[2] - reset csn to 0 a write to bit[0] of this register performs a reset function on all logical devices. this resets the contents of configuration registers to their default state. all card ? s logical devices enter their default state and the csn is preserved. a write to bit[1] of this register causes all cards to enter the wait for key state but all csns are preserved and logical devices are not affected. a write to bit[2] of this register causes all cards to reset their csn to zero. this register is write-only. the values are not sticky, that is, hardware will automatically clear them and there is no need for software to clear the bits. wake[csn] 0x03 a write to this port will cause all cards that have a csn that matches the write data[7:0] to go from the sleep state to either the isolation state if the write data for this command is zero or the config state if the write data is not zero. this register is write-only. writing to this register resets the eeprom pointer to the beginning of the plug and play data structure. resource data 0x04 a read from this address reads the next byte of resource information. the status register must be polled until bit[0] is set before this register may be read. this register is read-only. status 0x05 bit[0] when set indicates it is okay to read the next data byte from the resource data register. this register is read-only. card select number 0x06 a write to this port sets a card ? s csn. the csn is a value uniquely assigned to each isa card after the serial identification process so that each card may be individually selected during a wake [csn] command. this register is read/write. logical device number 0x07 selects the current logical device. this register is read only. the pcnet-isa ii controller has only 1 logical device, and this register contains a value of 0x00
54 am79c961a plug and play logical device configuration registers the pcnet-isa ii controller supports a subset of the defined plug and play logical device control registers. the reason for only supporting a subset of the registers is that the pcnet-isa ii controller does not require as many system resources as plug and play allows. for instance, memory descriptor 2 is not used, as the pc- net-isa ii controller only requires two memory descriptors, one for the boot prom/flash, and one for the sram in shared memory mode. plug and play logical device control registers memory space configuration i/o space configuration name address port value definition activate 0x30 for each logical device there is one activate register that controls whether or not the logical device is active on the isa bus. bit[0], if set, activates the logical device. bits[7:1] are reserved and must be zero. this is a read/write register. before a logical device is activated, i/o range check must be disabled. i/o range check 0x31 this register is used to perform a conflict check on the i/o port range programmed for use by a logical device. bit[7:2] reserved bit 1[1] enable i/o range check, if set then i/o range check is enabled. i/o range check is only valid when the logical device is inactive. bit[0], if set, forces the logical device to respond to i/o reads of the logical device ? s assigned i/o range with a 0x55 when i/o range check is in operation. if clear, the logical device drives 0xaa. this register is read/write. name register index definition memory base address bits[23:16] descriptor 0 0x40 read/write value indicating the selected memory base address bits[23:16] for memory descriptor 0. this is the boot prom space. memory base address bits [15:08] descriptor 0 0x41 read/write value indicating the selected memory base address bits[15:08] for memory descriptor 0. memory control 0x42 bit[1] specifies 8/16-bit control. the encoding relates to memory control (bits[4:3]) of the information field in the memory descriptor. bit[0], =0, indicates the next field is used as a range length for decode (implies range length and base alignment of memory descriptor are equal). bit[0] is read-only. memory upper limit address; bits [23:16] or range length; bits [15:08] for descriptor 0 0x43 read/write value indicating the selected memory high address bits[23:16] for memory descriptor 0. if bit[0] of memory control is 0, this is the range length. if bit[0] of memory control is 1, this is considered invalid. memory upper limit bits [15:08] or range length; bits [15:08] for descriptor 0 0x44 read/write value indicating the selected memory high address bits[15:08] for memory descriptor 0, either a memory address or a range length as described above. memory descriptor 1 0x48-0x4c memory descriptor 1. this is the sram space for shared memory. name register index definition i/o port base address bits[15:08] descriptor 0 0x60 read/write value indicating the selected i/o lower limit address bits[15:08] for i/o descriptor 0. if a logical device indicates it only uses 10 bit encoding, then bits[15:10] do not need to be supported. i/o port base address bits[07:00] descriptor 0 0x61 read/write value indicating the selected i/o lower limit address bits[07:00] for i/o descriptor 0.
am79c961a 55 i/o interrupt configuration dma channel configuration detailed functions eeprom interface the eeprom supported by the pcnet-isa ii controller is an industry standard 93c56 2-kbit eeprom device which uses a 4-wire interface. this device directly inter- faces to the pcnet-isa ii controller through a 4-wire interface which uses 3 of the private data bus pins for data in, data out, and serial clock. the chip select pin is a dedicated pin from the pcnet-isa ii controller. note : all data stored in the eeprom is stored in bit-re- versal format. each word (16 bits) must be written into the eeprom with bit 15 swapped with bit 0, bit 14 swapped with bit 1, etc. this is a 2-kbit device organized as 128 x 16 bit words. a map of the device as used in the pcnet-isa ii con- troller is below. the information stored in the eeprom is as follows: important note about the eeprom byte map the user is cautioned that while the am79c961a (pc- net-isa ii) and its associated eeprom are pin com- patible to their predecessors the am79c961 (pcnet-isa + ) and its associated eeprom, the byte map structure in each of the eeproms are different from each other. the eeprom byte map structure used for the am79c961a pcnet-isa ii has the addition of ? misc config 2, isacsr9" at word location 10hex. the eeprom byte map structure used for the am79c961 pcnet-isa+ does not have this. therefore, should the user intend to replace the pc- net-isa + with the pcnet-isa ii, care must be taken to reprogram the eeprom to reflect the new byte map structure needed and used by the pcnet-isa ii. for additional information, refer to the am79c961 pc- net-isa + data sheet (pid #18183) under the sections entitled eeprom and serial eeprom byte map . name register index definition interrupt request level select 0 0x70 read/write value indicating selected interrupt level. bits[3:0] select which interrupt level used for interrupt 0. one selects irql 1, fifteen selects irql fifteen. irql 0 is not a valid interrupt selection and represents no interrupt selection. interrupt request type select 0 0x71 read/write value indicating which type of interrupt is used for the request level selected above. bit[1] : level, 1 = high, 0 = low bit[0] : type, 1 = level, 0 = edge the pcnet-isa ii controller only supports edge high and level low interrupts. name register index definition dma channel select 0 0x74 read/write value indicating selected dma channels. bits[2:0] select which dma channel is in use for dma 0. zero selects dma channel 0, seven selects dma channel 7. dma channel 4, the cascade channel is used to indicate no dma channel is active. dma channel select 1 0x75 read only with a value of 0x04. ieee address 6 bytes reserved10 bytes eisa id4 bytes isacsrs14 bytes plug and play defaults19 bytes 8-bit checksum1 byte external shift chain2 bytes plug and play config info192 bytes
56 am79c961a basic eeprom byte map the following is a byte map of the xxc56 series of eeproms used by the pcnet-isa ii ethernet controller. this byte map is for the case where a non-pcnet family compatible software driver is implemented. note: checksum is calculated on words 0 through 0x1bh (first 56 bytes). byte 1 byte 3 byte 5 byte 7 byte 9 byte 11 byte 13 byte 15 eisa byte 1 eisa byte 3 byte 0 byte 2 byte 4 byte 6 byte 8 byte 10 byte 12 byte 14 eisa byte 0 eisa byte 2 msrda, isacsr0 mswra, isacsr1 misc config 1, isacsr2 led1 config, isacsr5 led2 config, isacsr6 led3 config, isacsr7 misc config 2, isacsr9 pnp 0x61 pnp 0x71 unused pnp 0x41 pnp 0x43 unused pnp 0x49 pnp 0x4b unused 8 ? bit checksum pnp 0x60 pnp 0x70 pnp 0x74 pnp 0x40 pnp 0x42 pnp 0x44 pnp 0x48 pnp 0x4a pnp 0x4c pnp 0xf0 external shift chain unused locations plug and play starting location ieee address (0h) (8h) internal registers (11h) plug and play reg. (1ah) (20h) eisa config reg. (ah) (1bh) (1ch) 0 1 2 3 4 5 6 7 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1b 1c 20 . . 1f word location i/o ports interrupts dma channels rom memory ram memory vendor byte (bytes 0 ? 5)
am79c961a 57 amd device driver compatible eeprom byte map the following is a byte map of the xxc56 series of eeproms used by the pcnet-isa ii ethernet controller. this byte map is for the case where a pcnet family compatible software driver is imple- mented. (this byte map is an application reference for use in developing amd software devices.) note: checksum 1 is calculated on words 0 through 5 plus word 7. checksum 2 is calculated on words 0 through 0x1bh (first 56 bytes). ieee address internal registers plug and play reg. see appendix c eisa config reg. 0 1 2 3 4 5 6 7 8 9 a b c d e f 11 12 13 14 15 16 17 18 19 1a 1b 1c 20 . . 1f word location i/o ports interrupts dma channels rom memory ram memory vendor byte see appendix c (bytes 0 ? 5) byte 1 byte 3 byte 5 ascii w (0 x 57h) eisa byte 1 eisa byte 3 byte 0 byte 2 byte 4 ascii w (0 x 57h) eisa byte 0 eisa byte 2 msrda, isacsr0 mswra, isacsr1 misc config, isacr2 led1 config, isacsr5 led2 config, isacsr6 led3 config, isacsr7 misc config 2, isacsr9 pnp 0x61 pnp 0x71 unused pnp 0x41 pnp 0x43 unused pnp 0x49 pnp 0x4b unused 8-bit checksum pnp 0x60 pnp 0x70 pnp 0x74 pnp 0x40 pnp 0x42 pnp 0x44 pnp 0x48 pnp 0x4a pnp 0x4c pnp 0xf0 external shift chain unused locations plug and play starting location user space 1 16-bit checksum 1 reserved hwid (01h) reserved reserved 10
58 am79c961a plug and play register map the following chart and its bit descriptions show the internal configuration registers associated with the plug and play operation. these registers control the configuration of the pcnet-isa ii controller. plug and play register bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00 read_data 0x01 serial isolation 0x02 0 0 0 0 0 rst wait rst csn key all 0x03 wake [csn] 0x04 resource_data 0x05 0 0 0 0 0 0 0 read status 0x06 csn 0x07 logical device number 0x30 0 0 0 0 0 0 0 activate 0x31 0 0 0 0 0 0 iorng iorng read_data address of plug and play read_data port. serial_isolation used in the serial isolation process. rst_csn resets csn register to zero. wait_key resets wait for key state. rst_all resets all logical devices. wake [csn] will wake up if write data matches csn register. read_status read status of resource data. resource_data next pending byte read from eeprom. csn plug and play csn value. activate indicates that the pcnet-isa ii device should be activated. iorng bits used to enable the i/o range check command.
am79c961a 59 the following chart and its bit descriptions show the internal command registers associated with the plug and play operation. these registers control the pc- net-isa ii controller plug and play operation. pcnet ? isa ii ? s legacy bit feature description the current pcnet-isa ii chip is designed such that it always responds to plug and play configuration soft- ware. there are situations where this response to the plug and play software is undesirable. an example of this is when a fixed configuration is required, or when the only possible resource available for the pcnet-isa ii conflicts with a present but not used resource such as irq, or when the chip is used in a system with a buggy pnp bios. to function in the situations above, a new feature has been added to the pcnet-isa ii chip. this new feature makes the chip ignore the pnp software ? s special initi- ation key sequence (6a). this will effectively turn the chip into the ? legacy ? mode operation, where it will be visible in the i/o space, and only special setup pro- grams will be able to reconfigure it. in case the eeprom is missing, empty, or corrupted, the chip will still recognize amd ? s special initiation key sequence (6b). to enable this feature, a one has to be written into the lgcy_en bit, which is bit 6 of the plug and play regis- ter 0xf0. a preferred method would be set this bit in the vendor byte (pnp 0xf0) field of the eeprom located in word offset 0x1a. plug and play register bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x60 0 0 0 0 0 0 1 ioam3 0x61 ioam2 ioam1 ioam0 0 0 0 0 0 0x70 0 0 0 0 irq3 irq2 irq1 irq0 0x71 0 0 0 0 0 0 irq_lvl irq_type 0x74 0 0 0 0 0 dma2 dma1 dma0 0x40 0 0 0 0 1 1 0 bpam3 0x41 bpam2 bpam1 bpam0 0 0 0 0 0 0x42 0 0 0 0 0 0 bp_16b 0 0x43 1 1 1 1 1 1 1 bpsz3 0x44 bpsz2 bpsz1 bpsz0 0 0 0 0 0 0x48 0 0 0 0 1 1 sram4 sram3 0x49 sram2 sram1 sram0 0 0 0 0 0 0x4a 0 0 0 0 0 0 sr16b 0 0x4b 1 1 1 1 1 1 1 srsz3 0x4c srsz2 srsz1 srsz0 0 0 0 0 0 0xf0 0 lgcy_en dxcvrp fl_sel bp_cs aprom_en aen_cs io_mode
60 am79c961a plug & play register locations detailed description (refer to the plug & play register map above) ioam[3:0] i/o address match to bits [8:5] of sa bus (pnp 0x60 ? 0x61). controls the base address of pcnet-isa ii. the ioam will be written with a value from the eeprom. irq[3:0] irq selection on the isa bus (pnp 0x70). controls which interrupt will be asserted. isa edge sensitive or eisa level mode is controlled by irq_type bit in pnp 0x71. default is isa edge sensitive. the irq sig- nals will not be driven unless pnp activate register bit is set. irq type irq type(pnp 0x71). indicates the type of interrupt setting; level is 1, edge is 0. irq_lvl irq level (pnp 0x71). a read-only regis- ter bit that indicates the type of setting, ac- tive high or low. always complement of irq_type. see isa csr2 (eisa_lvl). dma[2:0] dma channel select (pnp 0x74). controls the drq and dma selec- tion of pcnet-isa ii. the dma[2:0] register will be written with a value from the eeprom. {for bus master mode only} the drq signals will not be driven unless plug and play activate register bit is set. bpam[3:0] boot prom address match to bits [16:13] of sa bus (pnp 0x40 ? 0x41). selects the location where the boot prom address match decode is started. the bpam will be written with a value from the eeprom. bp_16b boot prom 16-bit access (pnp 0x42). is asserted if boot prom cycles should respond as an 16-bit device. in bus master mode, all boot prom cycles will only be 8 bits in width. bpsz[3:0] boot prom size (pnp 0x43 ? 0x44). selects the size of the boot prom selected. sram[4:0] static ram address match to bits [17:13] of sa bus (pnp 0x48-0x49). selects the starting location of the shared memory when using the ioam[3:0] base address (hex) 0000 200 0001 220 0010 240 0011 260 0100 280 0101 2a0 0110 2c0 0111 2e0 1000 300 1001 320 1010 340 1011 360 1100 380 1101 3a0 1110 3c0 1111 3e0 irq[3:0] isa irq pin 0 0 1 1 irq3 (default) 010 0irq4 010 1irq5 100 1irq9 101 0irq10 101 1irq11 110 1irq12 111 0irq15 dma[2:0] dma channel (drq/dack pair) 0 1 1 channel 3 1 0 1 channel 5 1 1 0 channel 6 1 1 1 channel 7 1 0 0 no dma channel bpam[3:0] address location (hex) size supported (k bytes) 0 0 0 0 c0000 8, 16, 32, 64 0001 c2000 8 0010 c4000 8, 16 0011 c6000 8 0100 c8000 8, 16, 32 0101 ca000 8 0 1 1 0 cc000 8, 16 0111 ce000 8 1 0 0 0 d0000 8, 16, 32, 64 1001 d2000 8 1010 d4000 8, 16 1011 d6000 8 1100 d8000 8, 16, 32 1101 da000 8 1 1 1 0 dc000 8, 16 1111 de000 8 bpsz[3:0] boot prom size 0 x x x no boot prom selected 11118 k 111016 k 110032 k 100064 k
am79c961a 61 shared memory architecture mode. the sram[2:0] bits are used for per- forming address decoding on the sa[15:13] address bits as shown in the table below. sram[4] and sram[3] must reflect the external address match logic for sa[17] and sa[16], respectively. the sram[4:0] bits are ignored when in the bus master mode or in the programmed i/o architecture mode. sr_16b static ram 16-bit access (pnp 0x4a). if asserted, the pcnet-isa ii will respond to sram cycles as a 16-bit device. this bit should be set if external logic is designed to assert the memcs16 signal when accesses to the shared memory are decoded. this bit is ignored when in the bus master mode or in the pro- grammed i/o architecture mode. srsz[3:0] static ram size (pnp 0x4b-0x4c). selects the size of the static ram. the srsz[3:0] bits are ignored when in the bus master mode or in the programmed i/o architecture mode. vendor defined byte (pnp 0xf0) lgcy_en legacy mode enable. when written with a one, the pcnet-isa ii will not respond to the plug and play initia- tion key sequence (6a) but will respond to the amd key sequence (6b). therefore, it cannot be recon- figured by the plug and play soft- ware. when set to zero (default), the pcnet-isa ii will respond to the 6a key sequence if the eeprom read was successful, otherwise it will re- spond to the 6b key sequence. dxcvrp dxcvr polarity. the dxcvrp bit sets the polarity of the dxcvr pin. when dxcvrp is cleared (default), the dxcvr pin is driven high when the twisted pair port is active or sleep mode has been entered and driven low when the aui port is active. when dxcvrp is set, the dxcvr pin is driven low when the twisted pair port is active or sleep mode has been entered and driven high when the aui port is active. the dxcvrp should generally be left cleared when the pcnet-isa ii is being used with an external dc-dc converter that has an active low enable pin. the dxcvrp should generally be set when the pc- net-isa ii is being used with an ex- ternal dc-dc converter that has an active high enable pin. io_mode i/o mode. when set to one, the internal selection will respond as a 16-bit port, (i.e. drive iocs16 pin). when io_mode is set to zero, (default), the internal i/o selection will respond as an 8-bit port. aen_cs external decode logic for i/o reg- isters. when written with a one, the pcnet-isa ii will use the aen pin as i/o chip select bar, to allow for exter- nal decode logic for the upper ad- dress bit of sa [9:5]. the purpose of this pin is to allow i/o locations, not supported with the ioam[3:0], selection, to be defined outside the range 0x200 ? 0x3f7. when set to a zero, (default), i/o selection will use ioam[3:0]. aprom_en external parallel ieee address prom. when set, the irq15 pin is reconfigured to be an address chip select low, similar to apcs pin in the existing pcnet-isa (am79c960) device. the purpose of this bit is to allow for both a serial eeprom and parallel prom to coexist. when aprom_en is set, the ieee address located in the serial ee- prom will be ignored and parallel access will occur over the prdb sram[2:0] sa[15:13] sram size (k bytes) 0000008, 16, 32, 64 0010018 0100108, 16 0110118 1001008, 16, 32 1011018 1101108, 16 111 1118 srsz[3:0] shared memory size 0 x x x no static ram selected 1111 8 k 1110 16 k 1100 32 k 1000 64 k
62 am79c961a bus. when aprom_en is cleared, default state, the ieee address will be read in from the serial device and written to an internal ram. when the i/o space of the ieee prom is selected, pcnet-isa ii, will access the contents of this ram for i/o read cycles. i/o write cycles will be ignored. bp_cs boot prom chip select. when bp_cs is set to one, bale will act as an external chip select (active low) above bit 15 of the address bus. bale = 0, will select the boot prom when memr is asserted low if the bp_cs bit is set and bpam[2:0] match sa[15:13] and bpsz[3:0] matches the selected size. when bp_cs is set to zero. bale will act as the normal address latch strobe to capture the upper address bits for memory access to the boot prom. bp_cs is by default low. the pri- mary purpose of this bit is to allow non-isa bus applications to support larger boot proms or non-standard boot prom/flash locations. fl_sel flash memory device selected. when set, the boot prom is replaced with an external flash memory device. in bus master mode, bpcs is replaced with flash _oe . irq12 becomes flash _we . the flash ? s cs pin is grounded. in shared memory mode, bpcs is replaced with flash _cs . irq12 becomes static _ram _cs pin. the sroe and srwe signals are connected to both the sram and flash memory devices. fl_sel is cleared by a reset, which is the default. checksum failure after reset, the pcnet-isa ii controller begins reading the eeprom and storing the information in registers inside pcnet-isa ii controller. pcnet-isa ii controller does a checksum on word locations 0-1bh inclusive and if the byte checksum = ffh, then the data read from the eeprom is considered good. if the checksum is not equal to ffh, then the pc- net-isa ii controller enters what is called software re- locatable mode. in software relocatable mode, the device functions the same as in plug and play mode, except that it does not respond to the same initiation key as plug and play supports. instead, a different key is used to bring pc- net-isa ii controller out of the wait for key state. this key is as follows: 6b, 35, 9a, cd, e6, f3, 79, bc 5e, af, 57, 2b, 15, 8a, c5, e2 f1, f8, 7c, 3e, 9f, 4f, 27, 13 09, 84, 42, a1, d0, 68, 34, 1a use without eeprom in some designs, especially pc motherboard applica- tions, it may be desirable to eliminate the eeprom altogether. this would save money, space, and power consumption. the operation of this mode is similar to when the pc- net-isa ii controller encounters a checksum error, ex- cept that to enter this mode the shfbusy pin is left unconnected. the device will enter software relocat- able mode, and the bios on the motherboard can wake up the device, configure it, load the ieee address (possibly stored in flash rom) into the pcnet-isa ii controller, and activate the device. external scan chain the external scan chain is a set of bits stored in the eeprom which are not used in the pcnet-isa ii con- troller but which can be used with external hardware to allow jumperless configuration of external devices. after reset, the pcnet-isa ii controller begins reading the eeprom and storing the informa- tion in registers inside the pcnet-isa ii controller. shfbusy is held high during the read of the eeprom. if external circuitry is added, such as a shift register, which is clocked from sclk and is attached to do from the eeprom, data read out of the eeprom will be shifted into the shift register. after reading the eeprom to the end of the external shift chain, and if there is a correct checksum, shfbusy will go low. this will be used to latch the information from the eeprom into the shift register. if the checksum is invalid, shfbusy will not go low, indicating that the eeprom may be bad. flash prom use instead of using a prom or eprom for the boot prom, it may be desirable to use a flash or eeprom type of device for storing the boot code. this would allow for in-system updates and changes to the infor- mation in the boot rom without opening up the pc. it may also be desirable to store statistics or drivers in the flash device.
am79c961a 63 interface to use a flash-type device with the pcnet-isa ii controller, flash select is set in register 0f0h of the plug and play registers. flash select is cleared by reset (default). in bus master mode, bpcs becomes flash _oe and irq12 becomes flash _we . the flash rom devices cs pin is connected to ground. in shared memory mode, bpcs becomes flash _cs and irq12 becomes the static ram chip select, and the sroe and srwe signals are connected to both the sram and flash devices. optional ieee address prom normally, the ethernet physical address will be stored in the eeprom with the other configuration data. this reduces the parts count, board space requirements, and power consumption. the option to use a standard parallel 8 bit prom is provided to manufacturers who are concerned about the non-volatile nature of eeproms. to use a 8 bit parallel prom to store the ieee address data instead of storing it in the eeprom, the aprom_en bit is set in the plug and play registers by the eeprom upon reset. irq15 is redefined by the setting of this bit to be apcs , or address prom chip select. this pin is connected to an external 8 bit prom, such as a 27ls19. the address pins of the prom are connected to the lower address pins of the isa bus, and the data lines are connected to the private data bus. in this mode, any accesses to the ieee address will be passed to the external prom and the data will be passed through the pcnet-isa ii controller to the system data bus. eisa configuration registers the pcnet-isa ii controller has support for the 4-byte eisa configuration registers. these are used in eisa systems to identify the card and load the appropriate configuration file for that card. this feature is enabled using bit 10 of isacsr2. when set to 1, the eisa configuration registers will be enabled and will be read at i/o location 0xc80 ? 0xc83. the contents of these 4 registers are stored in the eeprom and are automatically read in at reset. bus interface unit (biu) the bus interface unit is a mixture of a 20 mhz state machine and asynchronous logic. it handles two types of accesses; accesses where the pcnet-isa ii control- ler is a slave and accesses where the pcnet-isa ii con- troller is the current master. in slave mode, signals like iocs16 are asserted and deasserted as soon as the appropriate inputs are received. iochrdy is asynchronously driven low if the pcnet-isa ii controller needs a wait state. it is released synchronously when the pcnet-isa ii con- troller is ready. when the pcnet-isa ii controller is the current master, all the signals it generates are synchronous to the on-chip 20 mhz clock. dma transfers the biu will initiate dma transfers according to the type of operation being performed. there are three pri- mary types of dma transfers: 1. initialization block dma transfers during initialization, the pcnet-isa ii transfers 12 words from the initialization block in memory to internal registers. these 12 words are transferred through dif- ferent bus mastership period sequences, depending on whether the timer bit (csr4, bit 13) is set and, if timer is set, on the value in the bus activity timer register (csr82). if the timer bit is reset (default), the 12 words are always transferred during three separate bus master- ship periods. during each bus mastership period, four words (8 bytes) will be read from contiguous memory addresses. if the timer bit is set, the 12 words may be transferred using anywhere from 1 to 3 bus mastership periods, depending on the value of the bus activity timer regis- ter (csr82). during each bus mastership period, a minimum of four words (8 bytes) will be read from con- tiguous memory addresses. if the timer bit is set and the value in the bus activity timer register allows it, 8 or all 12 words of the initialization block are read during a single bus mastership period. 2. descriptor dma transfers descriptor dma transfers are performed to read or write to transmit or receive descriptors. all transmit and receive descriptor read accesses require 3 word reads (tmd1, tmd0, then tmd2 for transmit descrip- tors and rmd1, rmd0, then rmd2 for receive descrip- tors). transmit and receive descriptor write accesses to unchained descriptors or the last descrip- tor in a chain (enp set) require 2 word writes (tmd1 then tmd3 for transmit and rmd1 then rmd3 for re- ceive). transmit and receive descriptor write ac- cesses to chained descriptors that do not have enp set require 1 word write (tmd1 for transmit and rmd1 for receive). during descriptor write accesses, only the bytes which need to be written are written, as con- trolled by the sa0 and sbhe pins. if the timer bit is reset (default), all accesses during a single bus mastership period will be either all read or all write and will be to only one descriptor. hence, when the timer bit is reset, the bus mastership periods for
64 am79c961a descriptor accesses are always either 3, 2, or 1 cycles long, depending on which descriptor operation is being performed. if the timer bit is set, the 3, 2, or 1 cycles required in a descriptor access may be performed as a part of a bus mastership period in which any combination of descriptor reads and writes and buffer reads and writes are performed. when the timer bit is set, the bus activity timer (csr82) and the bus access require- ments of the pcnet-isa ii govern the operations per- formed during a single bus mastership period. 3. fifo dma transfers fifo dma transfers occur when the pcnet-isa ii microcode determines that transfers to and/or from the fifos are required. once the pcnet-isa ii biu has been granted bus mastership, it will perform a series of consecutive transfer cycles before relinquishing the bus. when the bus activity timer is disabled by clearing the timer (csr4, bit 13) bit, all fifo dma transfers within a bus mastership period will be either read or write cycles, and all transfers will be to adjacent, ascending addresses. when the bus activity timer is enabled by setting the timer bit, dma transfers within a bus mastership period may consist of any mixture of read and write cycles, without restriction on the address ordering. this mode of operation allows the pcnet-isa ii to accomplish more during each bus ownership period. the number of data transfer cycles contained within a single bus mastership period is in general dependent on the programming of the dmaplus (csr4, bit 14) and the timer (csr4, bit 13) options. several other factors will also affect the length of the bus mastership period. the possibilities are as follows: if dmaplus = 0 and timer = 0, a maximum of 16 transfers to or from the fifo will be performed by default. this default value may be changed by writing to the dma burst register (csr80, bits 7:0). since timer = 0, all fifo dma transfers within a bus mas- tership period will be either read or write cycles, and all transfers will be to adjacent, ascending addresses. note that dmaplus = 0 merely sets a maximum value for the number of fifo transfers that may occur during one bus mastership period. the minimum number of transfers in the bus mastership period will be deter- mined by the settings of the fifo watermarks and the conditions of the fifos, and the value of the bus activ- ity timer (csr82) if the timer bit is set. if dmaplus = 1 and timer = 0, the bus mastership period will continue until the transmit fifo is filled to its high threshold (read transfers) or the receive fifo is emptied to its low threshold (write transfers). other variables may also affect the end point of the bus mas- tership period in this mode, including the particular con- ditions existing within the fifos, and receive and transmit status conditions. since timer = 0, all fifo dma transfers within a bus mastership period will be either read or write cycles, and all transfers will be to adjacent, ascending addresses. if timer = 1, the bus mastership period will continue until all ? pending bus operations ? are completed or until the bus activity timer value (csr82) has expired. these bus operations may consist of any mixture of descriptor and buffer read and write accesses. if dma- plus = 1, ? pending bus operations ? includes any de- scriptor accesses and buffer accesses that need to be performed. if dmaplus = 0, ? pending bus operations ? include any descriptor accesses that need to be per- formed and any buffer accesses that need to be per- formed up to the limit specified by the dma burst register (csr80, bits 7:0). note that when timer=1, following a last bus transac- tion during a bus mastership period, the pcnet-isa ii may keep ownership of the bus for up to approximately 1 s. the pcnet-isa ii determines whether there are further pending bus operations by waiting approxi- mately 1 s after the completion of every bus operation (e.g. a descriptor or fifo access). if, during the 1 s period, no further bus operations are requested by the internal buffer management unit, the pcnet-isa ii determines that there are no further pending opera- tions and gives up bus ownership. this 1 s of unused bus ownership time is more than made up for by the efficiency gained by being able to perform any mixture of descriptor and buffer read and write accesses during a single bus ownership period. the fifo thresholds are programmable (see descrip- tion of csr80), as are the dma burst register and bus activity timer values. the exact number of transfer cycles in the case of dmaplus = 1 will be dependent on the latency of the system bus to the pcnet-isa ii controller ? s dma request and the speed of bus opera- tion, but will be limited by the value in the bus activity timer register (if the timer bit is set), the fifo condi- tion, and receive and transmit status. barring a time-out by either of these registers, or exceptional re- ceive and transmit events, or an end of packet signal from the fifo, the fifo watermark settings and the extent of bus grant latency will be the major factors de- termining the number of accesses performed during any given arbitration cycle when dmaplus = 1. the iochrdy response of the memory device will also affect the number of transfers when dmaplus = 1, since the speed of the accesses will af- fect the state of the fifo. during accesses, the fifo may be filling or emptying on the network end. a slower memory response will allow additional data to accumu- late inside of the fifo (during write transfers from the receive fifo). if the accesses are slow enough, a com-
am79c961a 65 plete word may become available before the end of the arbitration cycle and thereby increase the number of transfers in that cycle. the general rule is that the longer the bus grant latency or the slower the bus transfer operations (or clock speed) or the higher the transmit watermark or the lower the receive watermark or any combination thereof, the longer will be the aver- age bus mastership period. buffer management unit (bmu) the buffer management unit is a microcoded 20 mhz state machine which implements the initialization block and the descriptor architecture. initialization pcnet-isa ii controller initialization includes the read- ing of the initialization block in memory to obtain the operating parameters. the initialization block is read when the init bit in csr0 is set. the init bit should be set before or concurrent with the strt bit to insure cor- rect operation. see previous section ? 1. initialization block dma transfer. ? once the initialization block has been read in and processed, the bmu knows where the receive and transmit descriptor rings are. on comple- tion of the read operation and after internal registers have been updated, idon will be set in csr0, and an interrupt generated if iena is set. the initialization block is vectored by the contents of csr1 (least significant 16 bits of address) and csr2 (most significant 8 bits of address). the block contains the user defined conditions for pcnet-isa ii controller operation, together with the address and length infor- mation to allow linkage of the transmit and receive descriptor rings. there is an alternative method to initialize the pc- net-isa ii controller. instead of initialization via the ini- tialization block in memory, data can be written directly into the appropriate registers. either method may be used at the discretion of the programmer. if the regis- ters are written to directly, the init bit must not be set, or the initialization block will be read in, thus overwriting the previously written information. please refer to appendix d for details on this alternative method. reinitialization the transmitter and receiver section of the pcnet-isa ii controller can be turned on via the initialization block (mode register dtx, drx bits; csr15[1:0]). the state of the transmitter and receiver are monitored through csr0 (rxon, txon bits). the pcnet-isa ii controller should be reinitialized if the transmitter and/ or the receiver were not turned on during the original initialization and it was subsequently required to acti- vate them, or if either section shut off due to the detec- tion of an error condition (merr, uflo, tx buff error). reinitialization may be done via the initialization block or by setting the stop bit in csr0, followed by writing to csr15, and then setting the start bit in csr0. note that this form of restart will not perform the same in the pcnet-isa ii controller as in the lance. in par- ticular, the pcnet-isa ii controller reloads the transmit and receive descriptor pointers (working registers) with their respective base addresses. this means that the software must clear the descriptor ? s own bits and reset its descriptor ring pointers before the restart of the pc- net-isa controller. the reload of descriptor base addresses is performed in the lance only after initial- ization, so a restart of the lance without initialization leaves the lance pointing at the same descriptor locations as before the restart. suspend the pcnet-isa ii controller offers a suspend mode that allows easy updating of the csr registers without going through a full reinitialization of the device. the suspend mode also allows stopping the device with orderly termination of all network activity. the host requests the pcnet-isa ii controller to enter the suspend mode by setting spnd (csr5, bit 0) to one. the host must poll spnd until it reads back one to determine that the pcnet-isa ii controller has en- tered the suspend mode. when the host sets spnd to one, the pcnet-isa ii controller first finishes all on-go- ing transmit activity and updates the corresponding transmit descriptor entries. it then finishes all on-going receive activity and updates the corresponding receive descriptor entries. it then sets the read-version of spnd to one and enters the suspend mode. in sus- pend mode, all of the csr registers are accessible. as long as the pcnet-isa ii controller is not reset while in suspend mode (by asserting the reset pin, reading the reset register, or by setting the stop bit), no reinitialization of the device is required after the device comes out of suspend mode. when spnd is set to zero, the pcnet-isa ii controller will leave the sus- pend mode and will continue at the transmit and re- ceive descriptor ring locations where it had left when it entered the suspend mode. buffer management buffer management is accomplished through message descriptor entries organized as ring structures in mem- ory. there are two rings, a receive ring and a transmit ring. the size of a message descriptor entry is 4 words (8 bytes). descriptor rings each descriptor ring must be organized in a contiguous area of memory. at initialization time (setting the init bit in csr0), the pcnet-isa ii controller reads the user-defined base address for the transmit and receive descriptor rings, which must be on an 8-byte boundary, as well as the number of entries contained in the
66 am79c961a descriptor rings. by default, a maximum of 128 ring entries is permitted when utilizing the initialization block, which uses values of tlen and rlen to specify the transmit and receive descriptor ring lengths. how- ever, the ring lengths can be manually defined (up to 65535) by writing the transmit and receive ring length registers (csr76,78) directly. each ring entry contains the following information: the address of the actual message data buffer in user or host memory the length of the message buffer status information indicating the condition of the buffer receive descriptor entries are similar (but not identical) to transmit descriptor entries. both are composed of four registers, each 16 bits wide for a total of 8 bytes. to permit the queuing and de-queuing of message buffers, ownership of each buffer is allocated to either the pcnet-isa ii controller or the host. the own bit within the descriptor status information, either tmd or rmd (see section on tmd or rmd), is used for this purpose. ? deadly embrace ? conditions are avoided by the ownership mechanism. only the owner is permitted to relinquish ownership or to write to any field in the descriptor entry. a device that is not the current owner of a descriptor entry cannot assume ownership or change any field in the entry. descriptor ring access mechanism at initialization, the pcnet-isa ii controller reads the base address of both the transmit and receive descrip- tor rings into csrs for use by the pcnet-isa ii control- ler during subsequent operation. when transmit and receive functions begin, the base address of each ring is loaded into the current descrip- tor address registers and the address of the next descriptor entry in the transmit and receive rings is computed and loaded into the next descriptor address registers.
am79c961a 67 polling when there is no channel activity and there is no pre- or post-receive or transmit activity being performed by the pcnet-isa ii controller then the pcnet-isa ii con- troller will periodically poll the current receive and transmit descriptor entries in order to ascertain their ownership. if the dpoll bit in csr4 is set, then the transmit polling function is disabled. a typical polling operation consists of the following: the pcnet-isa ii controller will use the current receive descriptor address stored internally to vector to the appropriate receive descriptor table entry (rdte). it will then use the current transmit descriptor address (stored internally) to vector to the appropriate transmit descriptor table entry (tdte). these accesses will be made to rmd1 and rmd0 of the current rdte and tmd1 and tmd0 of the current tdte at periodic poll- initialization block 24-bit base address pointer to initialization block iadr[15:0] iadr[23:16] res csr1 csr2 tdra[15:0] mode padr[15:0] padr[31:16] padrf[47:32] ladrf[15:0] ladrf[31:16] ladrf[47:32] ladrf[63:48] rdra[15:0] rlen res rdra[23:16] tlen res tdra[23:16] rcv buffers rx descriptor rings rmd0 rmd1 rmd2 rmd3 rcv descriptor ring n n n n 1st desc. start 2nd desc. start rmd0 xmt buffers rx descriptor rings tmd0 tmd1 tmd2 tmd3 rx descriptor rings xmt descriptor ring m m m m 1st desc. start 2nd desc. start tmd0 data buffer 1 data buffer 2 data buffer n data buffer 1 data buffer 2 data buffer m 19364b-15 initialization block and descriptor rings
68 am79c961a ing intervals. all information collected during polling activity will be stored internally in the appropriate csrs. (i.e. csr18 ? 19, csr40, csr20 ? 21, csr42, csr50, csr52). unowned descriptor status will be internally ignored. a typical receive poll occurs under the following conditions: 1. pcnet-isa ii controller does not possess ownership of the current rdte and the poll time has elapsed and rxon = 1, or 2. pcnet-isa ii controller does not possess ownership of the next rdte and the poll time has elapsed and rxon = 1, if rxon = 0, the pcnet-isa ii controller will never poll rdte locations. if rxon = 1, the system should always have at least one rdte available for the possibility of a receive event. when there is only one rdte, there is no polling for next rdte. a typical transmit poll occurs under the following conditions: 1. pcnet-isa ii controller does not possess ownership of the current tdte and dpoll = 0 and txon = 1 and the poll time has elapsed, or 2. pcnet-isa ii controller does not possess ownership of the current tdte and dpoll = 0 and txon = 1 and a packet has just been received, or 3. pcnet-isa ii controller does not possess ownership of the current tdte and dpoll = 0 and txon = 1 and a packet has just been transmitted. the poll time interval is nominally defined as 32,768 crystal clock periods, or 1.6 ms. however, the poll time register is controlled internally by microcode, so any other microcode controlled operation will interrupt the incrementing of the poll count register. for example, when a receive packet is accepted by the pcnet-isa ii controller, the device suspends execution of the poll-time-incrementing microcode so that a receive microcode routine may instead be executed. poll-time-incrementing code is resumed when the receive operation has completely finished. note, how- ever, that following the completion of any receive or transmit operation, a poll operation will always be per- formed. the poll time count register is never reset. note that if a non-default is desired, then a strict se- quence of setting the init bit in csr0, waiting for the idon bit in csr0, then writing to csr47, and then set- ting strt in csr0 must be observed, otherwise the default value will not be overwritten. see the csr47 section for details. setting the tdmd bit of csr0 will cause the microcode controller to exit the poll counting code and immedi- ately perform a polling operation. if rdte ownership has not been previously established, then an rdte poll will be performed ahead of the tdte poll. transmit descriptor table entry (tdte) if, after a tdte access, the pcnet-isa ii controller finds that the own bit of that tdte is not set, then the pcnet-isa ii controller resumes the poll time count and re-examines the same tdte at the next expiration of the poll time count. if the own bit of the tdte is set, but stp = 0, the pc- net-isa ii controller will immediately request the bus in order to reset the own bit of this descriptor; this con- dition would normally be found following a lcol or retry error that occurred in the middle of a transmit packet chain of buffers. after resetting the own bit of this descriptor, the pcnet-isa ii controller will again immediately request the bus in order to access the next tdte location in the ring. if the own bit is set and the buffer length is 0, the own bit will be reset. in the lance the buffer length of 0 is interpreted as a 4096-byte buffer. it is acceptable to have a 0 length buffer on transmit with stp=1 or stp=1 and enp = 1. it is not acceptable to have 0 length buffer with stp = 0 and enp = 1. if the own bit is set and the start of packet (stp) bit is set, then microcode control proceeds to a routine that will enable transmit data transfers to the fifo. if the transmit buffers are data chained (enp = 0 in the first buffer), then the pcnet-isa ii controller will look ahead to the next transmit descriptor after it has per- formed at least one transmit data transfer from the first buffer. more than one transmit data transfer may possi- bly take place, depending upon the state of the trans- mitter. the transmit descriptor look ahead reads tmd0 first and tmd1 second. the contents of tmd0 and tmd1 will be stored in next tx descriptor address (csr32), next tx byte count (csr66) and next tx status (csr67) regardless of the state of the own bit. this transmit descriptor lookahead operation is performed only once. if the pcnet-isa ii controller does not own the next tdte (i.e. the second tdte for this packet), then it will complete transmission of the current buffer and then
am79c961a 69 update the status of the current (first) tdte with the buff and uflo bits being set. if dxsuflo is 0 (bit 6 csr3), then this will cause the transmitter to be dis- abled (csr0, txon = 0). the pcnet-isa ii controller will have to be restarted to restore the transmit function. the situation that matches this description implies that the system has not been able to stay ahead of the pc- net-isa ii controller in the transmit descriptor ring and therefore, the condition is treated as a fatal error. to avoid this situation, the system should always set the transmit chain descriptor own bits in reverse order. if the pcnet-isa ii controller does own the second tdte in a chain, it will gradually empty the contents of the first buffer (as the bytes are needed by the transmit operation), perform a single-cycle dma transfer to update the status (reset the own bit in tmd1) of the first descriptor, and then it may perform one data dma access on the second buffer in the chain before execut- ing another lookahead operation. (i.e. a lookahead to the third descriptor). the pcnet-isa ii controller can queue up to two pack- ets in the transmit fifo. call them packet ? x ? and packet ? y ? , where ? y ? is after ? x ? . assume that packet ? x ? is currently being transmitted. because the pc- net-isa ii controller can perform lookahead data trans- fer over an enp, it is possible for the pcnet-isa ii controller to update a tdte in a buffer belonging to packet ? y ? while packet ? x ? is being transmitted if packet ? y ? uses data chaining. this operation will result in non-sequential tdte accesses as packet ? x ? com- pletes transmission and the pcnet-isa ii controller writes out its status, since packet ? x ?? s tdte is before the tdte accessed as part of the lookahead data transfer from packet ? y ? . this should not cause any problem for properly written software which processes buffers in sequence, waiting for ownership before proceeding. if an error occurs in the transmission before all of the bytes of the current buffer have been transferred, then tmd2 and tmd1 of the current buffer will be written; in that case, data transfers from the next buffer will not commence. instead, following the tmd2/tmd1 up- date, the pcnet-isa ii controller will go to the next transmit packet, if any, skipping over the rest of the packet which experienced an error, including chained buffers. this is done by returning to the polling microcode where it will immediately access the next descriptor and find the condition own = 1 and stp = 0 as described earlier. in that case, the pcnet-isa ii control- ler will reset the own bit for this descriptor and continue in like manner until a descriptor with own = 0 (no more transmit packets in the ring) or own = 1 and stp = 1 (the first buffer of a new packet) is reached. at the end of any transmit operation, whether success- ful or with errors, and the completion of the descriptor updates, the pcnet-isa ii controller will always perform another poll operation. as described earlier, this poll operation will begin with a check of the current rdte, unless the pcnet-isa ii controller already owns that descriptor. then the pcnet-isa ii controller will proceed to polling the next tdte. if the transmit descriptor own bit has a zero value, then the pc- net-isa ii controller will resume poll time count incrementation. if the transmit descriptor own bit has a value of one, then the pcnet-isa ii controller will begin filling the fifo with transmit data and initiate a transmission. this end-of-operation poll avoids insert- ing poll time counts between successive transmit packets. whenever the pcnet-isa ii controller completes a transmit packet (either with or without error) and writes the status information to the current descriptor, then the tint bit of csr0 is set to indicate the completion of a transmission. this causes an interrupt signal if the iena bit of csr0 has been set and the tintm bit of csr3 is reset. receive descriptor table entry (rdte) if the pcnet-isa ii controller does not own both the cur- rent and the next receive descriptor table entry, then the pcnet-isa ii controller will continue to poll accord- ing to the polling sequence described above. if the receive descriptor ring length is 1, there is no next descriptor, and no look ahead poll will take place. if a poll operation has revealed that the current and the next rdte belongs to the pcnet-isa ii controller, then additional poll accesses are not necessary. future poll operations will not include rdte accesses as long as the pcnet-isa ii controller retains ownership to the cur- rent and the next rdte. when receive activity is present on the channel, the pcnet-isa ii controller waits for the complete address of the message to arrive. it then decides whether to accept or reject the packet based on all active address- ing schemes. if the packet is accepted the pcnet-isa ii controller checks the current receive buffer status reg- ister crst (csr40) to determine the ownership of the current buffer. if ownership is lacking, then the pcnet-isa ii controller will immediately perform a (last ditch) poll of the current rdte. if ownership is still denied, then the pcnet-isa ii controller has no buffer in which to store the incoming message. the miss bit will be set in csr0 and an interrupt will be generated if iena = 1 (csr0) and missm = 0 (csr3). another poll of the current rdte will not occur until the packet has finished. if the pcnet-isa ii controller sees that the last poll (either a normal poll or the last-ditch effort described in
70 am79c961a the above paragraph) of the current rdte shows valid ownership, then it proceeds to a poll of the next rdte. following this poll, and regardless of the outcome of this poll, transfers of receive data from the fifo may begin. regardless of ownership of the second receive descriptor, the pcnet-isa ii controller will continue to perform receive data dma transfers to the first buffer, using burst-cycle dma transfers. if the packet length exceeds the length of the first buffer, and the pc- net-isa ii controller does not own the second buffer, ownership of the current descriptor will be passed back to the system by writing a zero to the own bit of rmd1 and status will be written indicating buffer (buff = 1) and possibly overflow (oflo = 1) errors. if the packet length exceeds the length of the first (cur- rent) buffer, and the pcnet-isa ii controller does own the second (next) buffer, ownership will be passed back to the system by writing a zero to the own bit of rmd1 when the first buffer is full. receive data trans- fers to the second buffer may occur before the pc- net-isa ii controller proceeds to look ahead to the ownership of the third buffer. such action will depend upon the state of the fifo when the status has been updated on the first descriptor. in any case, lookahead will be performed to the third buffer and the information gathered will be stored in the chip, regardless of the state of the ownership bit. as in the transmit flow, loo- kahead operations are performed only once. this activity continues until the pcnet-isa ii controller recognizes the completion of the packet (the last byte of this receive message has been removed from the fifo). the pcnet-isa ii controller will subsequently up- date the current rdte status with the end of packet (enp) indication set, write the message byte count (mcnt) of the complete packet into rmd2 and over- write the ? current ? entries in the csrs with the ? next ? en- tries. media access control the media access control engine incorporates the essential protocol requirements for operation of a com- pliant ethernet/802.3 node, and provides the interface between the fifo sub-system and the manchester encoder/decoder (mendec). this section describes operation of the mac engine when operating in half duplex mode. when in half duplex mode, the mac engine is fully compliant to sec- tion 4 of iso/iec 8802-3 (ansi/ieee standard 1990 second edition) and ansi/ieee 802.3 (1985). when operating in full duplex mode, the mac engine behavior changes as described in the full duplex operation sec- tion. the mac engine provides programmable enhanced features designed to minimize host supervision and pre or post-message processing. these features include the ability to disable retries after a collision, dynamic fcs generation on a packet-by-packet basis, and au- tomatic pad field insertion and deletion to enforce minimum frame size attributes. the two primary attributes of the mac engine are: transmit and receive message data encapsulation ? framing (frame boundary delimitation, frame synchronization) ? addressing (source and destination address handling) ? error detection (physical medium transmission errors) media access management ? medium allocation (collision avoidance) ? contention resolution (collision handling) transmit and receive message data encapsulation the mac engine provides minimum frame size enforcement for transmit and receive packets. when apad_xmt = 1 (bit 11 in csr4), transmit messages will be padded with sufficient bytes (containing 00h) to ensure that the receiving station will observe an infor- mation field (destination address, source address, length/type, data and fcs) of 64-bytes. when astrp_rcv = 1 (bit 10 in csr4), the receiver will automatically strip pad bytes from the received mes- sage by observing the value in the length field, and stripping excess bytes if this value is below the mini- mum data size (46 bytes). both features can be inde- pendently over-ridden to allow illegally short (less than 64 bytes of packet data) messages to be transmitted and/or received. the use of these features reduce bus bandwidth usage because the pad bytes are not trans- ferred to or from host memory. framing (frame boundary delimitation, frame synchronization) the mac engine will autonomously handle the con- struction of the transmit frame. once the transmit fifo has been filled to the predetermined threshold (set by xmtsp in csr80), and providing access to the chan- nel is currently permitted, the mac engine will com- mence the 7-byte preamble sequence (10101010b, where first bit transmitted is a 1). the mac engine will subsequently append the start frame delimiter (sfd) byte (10101011b) followed by the serialized data from the transmit fifo. once the data has been completed, the mac engine will append the fcs (most significant bit first) which was computed on the entire data portion of the message. note that the user is responsible for the correct order- ing and content in each of the fields in the frame,
am79c961a 71 including the destination address, source address, length/type and packet data. the receive section of the mac engine will detect an incoming preamble sequence and lock to the encoded clock. the internal mendec will decode the serial bit stream and present this to the mac engine. the mac will discard the first 8 bits of information before search- ing for the sfd sequence. once the sfd is detected, all subsequent bits are treated as part of the frame. the mac engine will inspect the length field to ensure min- imum frame size, strip unnecessary pad characters (if enabled), and pass the remaining bytes through the receive fifo to the host. if pad stripping is performed, the mac engine will also strip the received fcs bytes, although the normal fcs computation and checking will occur. note that apart from pad stripping, the frame will be passed unmodified to the host. if the length field has a value of 46 or greater, the mac engine will not attempt to validate the length against the number of bytes contained in the message. if the frame terminates or suffers a collision before 64 bytes of information (after sfd) have been received, the mac engine will automatically delete the frame from the receive fifo, without host intervention. addressing (source and destination address handling) the first 6 bytes of information after sfd will be inter- preted as the destination address field. the mac engine provides facilities for physical, logical, and broadcast address reception. in addition, multiple physical addresses can be constructed (perfect address filtering) using external logic in conjunction with the eadi interface. error detection (physical medium transmission errors) the mac engine provides several facilities which report and recover from errors on the medium. in addi- tion, the network is protected from gross errors due to inability of the host to keep pace with the mac engine activity. on completion of transmission, the following transmit status is available in the appropriate tmd and csr areas: the exact number of transmission retry attempts (one, more, or rtry). whether the mac engine had to defer (def) due to channel activity. loss of carrier, indicating that there was an inter- ruption in the ability of the mac engine to monitor its own transmission. repeated lcar errors indicate a potentially faulty transceiver or network connection. late collision (lcol) indicates that the transmis- sion suffered a collision after the slot time. this is indicative of a badly configured network. late colli- sions should not occur in a normal operating net- work. collision error (cerr) indicates that the trans- ceiver did not respond with an sqe test message within the predetermined time after a transmission completed. this may be due to a failed transceiver, disconnected or faulty transceiver drop cable, or the fact the transceiver does not support this feature (or the feature is disabled). in addition to the reporting of network errors, the mac engine will also attempt to prevent the creation of any network error due to the inability of the host to service the mac engine. during transmission, if the host fails to keep the transmit fifo filled sufficiently, causing an underflow, the mac engine will guarantee the message is either sent as a runt packet (which will be deleted by the receiving station) or has an invalid fcs (which will also cause the receiver to reject the message). the status of each receive message is available in the appropriate rmd and csr areas. fcs and framing errors (fram) are reported, although the received frame is still passed to the host. the fram error will only be reported if an fcs error is detected and there are a non-integral number of bits in the message. the mac engine will ignore up to seven additional bits at the end of a message (dribbling bits), which can occur under normal network operating conditions. the recep- tion of eight additional bits will cause the mac engine to de-serialize the entire byte, and will result in the received message and fcs being modified. the pcnet-isa ii controller can handle up to 7 dribbling bits when a received packet terminates. during the reception, the crc is generated on every serial bit (including the dribbling bits) coming from the cable, although the internally saved crc value is only updated on the eighth bit (on each byte boundary). the framing error is reported to the user as follows: 1. if the number of the dribbling bits are 1 to 7 and there is no crc error, then there is no framing error (fram = 0). 2. if the number of the dribbling bits are less than 8 and there is a crc error, then there is also a framing error (fram = 1). 3. if the number of dribbling bits = 0, then there is no framing error. there may or may not be a crc (fcs) error. counters are provided to report the receive collision count and runt packet count used for network statis- tics and utilization calculations. note that if the mac engine detects a received packet which has a 00b pattern in the preamble (after the first
72 am79c961a 8 bits, which are ignored), the entire packet will be ignored. the mac engine will wait for the network to go inactive before attempting to receive the next packet. media access management the basic requirement for all stations on the network is to provide fairness of channel allocation. the 802.3/ ethernet protocol defines a media access mechanism which permits all stations to access the channel with equality. any node can attempt to contend for the chan- nel by waiting for a predetermined time (inter packet gap interval) after the last activity, before transmitting on the medium. the channel is a multidrop communications medium (with various topological con- figurations permitted) which allows a single station to transmit and all other stations to receive. if two nodes simultaneously contend for the channel, their signals will interact, causing loss of data (defined as a collision). it is the responsibility of the mac to attempt to avoid and recover from a collision, to guarantee data integrity for the end-to-end transmission to the receiving station. medium allocation (collision avoidance) the ieee 802.3 standard (iso/iec 8802-3 1990) requires that the csma/cd mac monitor the medium traffic by looking for carrier activity. when carrier is detected the medium is considered busy, and the mac should defer to the existing message. the ieee 802.3 standard also allows optional two part deferral after a receive message. see ansi/ieee std 802.3-1990 edition, 4.2.3.2.1: ?note : it is possible for the pls carrier sense indication to fail to be asserted during a colli- sion on the media. if the deference process simply times the interpacket gap based on this indication it is possible for a short interframe gap to be generated, leading to a potential re- ception failure of a subsequent frame. to en- hance system robustness the following option- al measures, as specified in 4.2.8, are recom- mended when interframespacingpart1 is other than zero: (1) upon completing a transmission, start timing the interpacket gap, as soon as transmitting and carrier sense are both false. (2) when timing an interpacket gap following re- ception, reset the interpacket gap timing if car- rier sense becomes true during the first 2/3 of the interpacket gap timing interval. during the final 1/3 of the interval the timer shall not be re- set to ensure fair access to the medium. an ini- tial period shorter than 2/3 of the interval is permissible including zero.? the mac engine implements the optional receive two part deferral algorithm, with a first part in- ter-frame-spacing time of 6.0 s. the second part of the inter-frame-spacing interval is therefore 3.6 s. the pcnet-isa ii controller will perform the two-part deferral algorithm as specified in section 4.2.8 (pro- cess deference). the inter packet gap (ipg) timer will start timing the 9.6 s interframespacing after the receive carrier is de-asserted. during the first part deferral (interframespacingpart1 ? ifs1) the pc- net-isa ii controller will defer any pending transmit frame and respond to the receive message. the ipg counter will be reset to zero continuously until the car- rier de-asserts, at which point the ipg counter will resume the 9.6 s count once again. once the ifs1 period of 6.0 s has elapsed, the pcnet-isa ii control- ler will begin timing the second part deferral (interframespacingpart2 ? ifs2) of 3.6 s. once ifs1 has completed, and ifs2 has commenced, the pc- net-isa ii controller will not defer to a receive packet if a transmit packet is pending. this means that the pc- net-isa ii controller will not attempt to receive the re- ceive packet, since it will start to transmit, and generate a collision at 9.6 s. the pcnet-isa ii controller will guarantee to complete the preamble (64-bit) and jam (32-bit) sequence before ceasing transmission and invoking the random backoff algorithm. in addition, transmit two part deferral is implemented as an option which can be disabled using the dxmt2pd bit (csr3). two-part deferral after trans- mission is useful for ensuring that severe ipg shrink- age cannot occur in specific circumstances, causing a transmit message to follow a receive message so closely as to make them indistinguishable. during the time period immediately after a transmission has been completed, the external transceiver (in the case of a standard aui connected device), should gen- erate the sqe test message (a nominal 10 mhz burst of 5-15 bit times duration) on the ci pair (within 0.6 s ? 1.6 s after the transmission ceases). during the time period in which the sqe test message is expected the pcnet-isa ii controller will not respond to receive car- rier sense. see ansi/ieee std 802.3-1990 edition, 7.2.4.6 (1): ? at the conclusion of the output function, the dte opens a time window during which it ex- pects to see the signal_quality_erro r signal as- serted on the control in circuit. the time win- dow begins when the carrier_status be- comes carrier_off. if execution of the out- put function does not cause carrier_on to occur, no sqe test occurs in the dte. the du- ration of the window shall be at least 4.0 s but no more than 8.0 s. during the time window the carrier sense function is inhibited. ? the pcnet-isa ii controller implements a carrier sense ? blinding ? period within 0 ? 4.0 s from de-assertion of carrier sense after transmission. this effectively means that when transmit two part deferral is enabled (dxmt2pd is cleared) the ifs1 time is from 4 s to 6
am79c961a 73 s after a transmission. however, since ipg shrinkage below 4 s will rarely be encountered on a correctly configured network, and since the fragment size will be larger than the 4 s blinding window, then the ipg counter will be reset by a worst case ipg shrinkage/ fragment scenario and the pcnet-isa ii controller will defer its transmission. in addition, the pcnet-isa ii controller will not restart the ? blinding ? period if carrier is detected within the 4.0 s ? 6.0 s ifs1 period, but will commence timing of the entire ifs1 period. contention resolution (collision handling) collision detection is performed and reported to the mac engine by the integrated manchester encoder/ decoder (mendec). if a collision is detected before the complete preamble/ sfd sequence has been transmitted, the mac engine will complete the preamble/sfd before appending the jam sequence. if a collision is detected after the pream- ble/sfd has been completed, but prior to 512 bits being transmitted, the mac engine will abort the trans- mission, and append the jam sequence immediately. the jam sequence is a 32-bit all zeroes pattern. the mac engine will attempt to transmit a frame a total of 16 times (initial attempt plus 15 retries) due to normal collisions (those within the slot time). detection of colli- sion will cause the transmission to be re-scheduled, dependent on the backoff time that the mac engine computes. if a single retry was required, the one bit will be set in the transmit frame status (tmd1 in the transmit descriptor ring). if more than one retry was required, the more bit will be set. if all 16 attempts ex- perienced collisions, the rtry bit (in tmd3) will be set (one and more will be clear), and the transmit mes- sage will be flushed from the fifo. if retries have been disabled by setting the drty bit in the mode register (csr15), the mac engine will abandon transmission of the frame on detection of the first collision. in this case, only the rtry bit will be set and the transmit message will be flushed from the fifo. if a collision is detected after 512 bit times have been transmitted, the collision is termed a late collision. the mac engine will abort the transmission, append the jam sequence, and set the lcol bit. no retry attempt will be scheduled on detection of a late collision, and the fifo will be flushed. the ieee 802.3 standard requires use of a ? truncated binary exponential backoff ? algorithm which provides a controlled pseudo-random mechanism to enforce the collision backoff interval, before re-transmission is attempted. see ansi/ieee std 802.3-1990 edition, 4.2.3.2.5: ? at the end of enforcing a collision (jamming), the csma/cd sublayer delays before attempt- ing to re-transmit the frame. the delay is an in- teger multiple of slot time. the number of slot times to delay before the nth re-transmission attempt is chosen as a uniformly distributed random integer r in the range: 0 r < 2 k , where k = min (n,10). ? the pcnet-isa ii controller provides an alternative algorithm, which suspends the counting of the slot time/ipg during the time that receive carrier sense is detected. this algorithm aids in networks where large numbers of nodes are present, and numerous nodes can be in collision. the algorithm effectively acceler- ates the increase in the backoff time in busy networks, and allows nodes not involved in the collision to access the channel while the colliding nodes await a reduction in channel activity. once channel activity is reduced, the nodes resolving the collision time out their slot time counters as normal. manchester encoder/decoder (mendec) the integrated manchester encoder/decoder provides the pls (physical layer signaling) functions required for a fully compliant ieee 802.3 station. the mendec provides the encoding function for data to be transmit- ted on the network using the high accuracy on-board oscillator, driven by either the crystal oscillator or an ex- ternal cmos-level compatible clock. the mendec also provides the decoding function from data received from the network. the mendec contains a power on reset (por) circuit, which ensures that all analog por- tions of the pcnet-isa ii controller are forced into their correct state during power-up, and prevents erroneous data transmission and/or reception during this time. external crystal characteristics when using a crystal to drive the oscillator, the crystal specification shown in the specification table may be used to ensure less than 0.5 ns jitter at do .
74 am79c961a external crystal characteristics requires trimming crystal spec; no trim is 50 ppm total parameter min nom max unit 1. parallel resonant frequency 20 mhz 2. resonant frequency error (cl = 20 pf) ? 50 +50 ppm 3.change in resonant frequency with respect to temperature (0 ? 70 c; cl = 20 pf)* ? 40 +40 ppm 4. crystal capacitance 20 pf 5. motional crystal capacitance (c1) 0.022 pf 6. series resistance 25 ? 7. shunt capacitance 7 pf 8. drive level tbd mw
am79c961a 75 external clock drive characteristics when driving the oscillator from an external clock source, xtal2 must be left floating (unconnected). an external clock having the following characteristics must be used to ensure less than 0.5 ns jitter at do . mendec transmit path the transmit section encodes separate clock and nrz data input signals into a standard manchester encoded serial bit stream. the transmit outputs (do ) are designed to operate into terminated transmission lines. when operating into a 78 ? terminated transmission line, the transmit signaling meets the required output levels and skew for cheapernet, ethernet, and ieee-802.3. transmitter timing and operation a 20 mhz fundamental-mode crystal oscillator pro- vides the basic timing reference for the mendec por- tion of the pcnet-isa ii controller. the crystal input is divided by two to create the internal transmit clock ref- erence. both clocks are fed into the manchester encoder to generate the transitions in the encoded data stream. the internal transmit clock is used by the mendec to internally synchronize the internal trans- mit data (itxdat) from the controller and internal transmit enable (itxen). the internal transmit clock is also used as a stable bit-rate clock by the receive sec- tion of the mendec and controller. the oscillator requires an external 0.005% crystal, or an external 0.01% cmos-level input as a reference. the accuracy requirements, if an external crystal is used, are tighter because allowance for the on-chip oscillator must be made to deliver a final accuracy of 0.01%. transmission is enabled by the controller. as long as the itxen request remains active, the serial output of the controller will be manchester encoded and appear at do . when the internal request is dropped by the controller, the differential transmit outputs go to one of two idle states, dependent on tsel in the mode register (csr15, bit 9): receive path the principal functions of the receiver are to signal the pcnet-isa ii controller that there is information on the receive pair, and to separate the incoming manchester encoded data stream into clock and nrz data. the receiver section (see receiver block diagram) consists of two parallel paths. the receive data path is a zero threshold, wide bandwidth line receiver. the carrier path is an offset threshold bandpass detecting line receiver. both receivers share common bias networks to allow operation over a wide input common mode range. input signal conditioning transient noise pulses at the input data stream are rejected by the noise rejection filter. pulse width rejection is proportional to transmit data rate which is fixed at 10 mhz for ethernet systems but which could be different for proprietary networks. dc inputs more negative than minus 100 mv are also suppressed. the carrier detection circuitry detects the presence of an incoming data packet by discerning and rejecting noise from expected manchester data, and controls the stop and start of the phase-lock loop during clock acquisition. clock acquisition requires a valid manchester bit pattern of 1010b to lock onto the incom- ing message. when input amplitude and pulse width conditions are met at di , a clock acquisition cycle is initiated. clock acquisition when there is no activity at di (receiver is idle), the receive oscillator is phase-locked to stdclk. the first negative clock transition (bit cell center of first valid manchester ? 0") after clock acquisition begins inter- rupts the receive oscillator. the oscillator is then restarted at the second manchester ? 0" (bit time 4) and is phase-locked to it. as a result, the mendec acquires the clock from the incoming manchester bit pattern in 4 bit times with a ? 1010" manchester bit pat- tern. the internal receiver clock, irxclk, and the internal received data, irxdat, are enabled 1/4 bit time after clock acquisition in bit cell 5. irxdat is at a high state when the receiver is idle (no irxclk). irxdat how- ever, is undefined when clock is acquired and may remain high or change to low state whenever irx- clk is enabled. at 1/4 bit time through bit cell 5, the controller portion of the pcnet-isa ii controller sees the first irxclk transition. this also strobes in the incoming fifth bit to the mendec as manchester ? 1". irxdat may make a transition after the irxclk rising edge in bit cell 5, but its state is still undefined. the manchester ? 1" at bit 5 is clocked to irxdat output at 1/4 bit time in bit cell 6. clock frequency: 20 mhz 0.01 % rise/fall time (tr/tf): < 6 ns from 0.5 v to v dd ? 0.5 xtal1 high/low time (thigh/tlow): 40 ? 60% duty cycle xtal1 falling edge to falling edge jitter: < 0.2 ns at 2.5 v input (vdd/2) tsel low: the idle state of do yields ? zero ? differential to operate transformer-coupled loads tsel high: in this idle state, do+ is positive with respect to do ? (logical high).
76 am79c961a pll tracking after clock acquisition, the phase-locked clock is com- pared to the incoming transition at the bit cell center (bcc) and the resulting phase error is applied to a cor- rection circuit. this circuit ensures that the phase-locked clock remains locked on the received signal. individual bit cell phase corrections of the voltage controlled oscillator (vco) are limited to 10% of the phase difference between bcc and phase- locked clock. receiver block diagram carrier tracking and end of message the carrier detection circuit monitors the di inputs after irxcrs is asserted for an end of message. irxcrs de-asserts 1 to 2 bit times after the last posi- tive transition on the incoming message. this initiates the end of reception cycle. the time delay from the last rising edge of the message to irxcrs deassert allows the last bit to be strobed by irxclk and transferred to the controller section, but prevents any extra bit(s) at the end of message. when irxcrs de-asserts an irxcrs hold off timer inhibits irxcrs assertion for at least 2 bit times. data decoding the data receiver is a comparator with clocked output to minimize noise sensitivity to the di inputs. input error is less than 35 mv to minimize sensitivity to input rise and fall time. irxclk strobes the data receiver output at 1/4 bit time to determine the value of the manchester bit, and clocks the data out on irxdat on the following irxclk. the data receiver also generates the signal used for phase detector compari- son to the internal mendec voltage controlled oscillator (vco). differential input terminations the differential input for the manchester data (di ) should be externally terminated by two 40.2 ? 1% resistors and one optional common-mode bypass capacitor, as shown in the differential input termina- tion diagram below. the differential input impedance, z idf , and the common-mode input impedance, z icm , are specified so that the ethernet specification for cable termination impedance is met using standard 1% resistor terminators. if sip devices are used, 39 ? is the nearest usable equivalent value. the ci differen- tial inputs are terminated in exactly the same way as the di pair. collision detection a mau detects the collision condition on the network and generates a differential signal at the ci inputs. this collision signal passes through an input stage which detects signal levels and pulse duration. when the signal is detected by the mendec it sets the inter- nal collision signal, iclsn, high. the condition contin- data receiver manchester decoder noise reject filter carrier detect circuit *internal signal di irxdat* irxclk* irxcrs* 19364b-16 pcnet-isa ii di+ di 40.2 ? 40.2 ? 0.01 f to 0.1 f aui isolation transformer differential input termination 19364a-17
am79c961a 77 ues for approximately 1.5 bit times after the last low-to-high transition on ci . jitter tolerance definition the mendec utilizes a clock capture circuit to align its internal data strobe with an incoming bit stream. the clock acquisition circuitry requires four valid bits with the values 1010b. clock is phase-locked to the nega- tive transition at the bit cell center of the second ? 0" in the pattern. since data is strobed at 1/4 bit time, manchester tran- sitions which shift from their nominal placement through 1/4 bit time will result in improperly decoded data. with this as the criteria for an error, a definition of ? jitter handling ? is: the peak deviation approaching or crossing 1/4 bit cell position from nominal input transi- tion, for which the mendec section will properly decode data. attachment unit interface (aui) the aui is the pls (physical layer signaling) to pma (physical medium attachment) interface which con- nects the dte to a mau. the differential interface pro- vided by the pcnet-isa ii controller is fully compliant with section 7 of iso 8802-3 (ansi/ieee 802.3). after the pcnet-isa ii controller initiates a transmis- sion, it will expect to see data ? looped-back ? on the di pair (when the aui port is selected). this will internally generate a ? carrier sense ? , indicating that the integrity of the data path to and from the mau is intact, and that the mau is operating correctly. this ? carrier sense ? sig- nal must be asserted within sometime before end of transmission. if ? carrier sense ? does not become active in response to the data transmission, or becomes inac- tive before the end of transmission, the loss of carrier (lcar) error bit will be set in the transmit descriptor ring (tmd3, bit 11) after the packet has been transmitted. twisted pair transceiver (t-mau) this section describes operation of the t-mau when operating in the half duplex mode. when in half duplex mode, the t-mau implements the medium attachment unit (mau) functions for the twisted pair medium as specified by the supplement to ieee 802.3 standard (type 10base-t). when operating in full duplex mode, the mac engine behavior changes as described in the full duplex operation section. the t-mau provides twisted pair driver and receiver cir- cuits, including on-board transmit digital predistortion and receiver squelch, and a number of additional fea- tures including link status indication, automatic twisted pair receive polarity detection/correction and indication, receive carrier sense, transmit active and collision present indication. twisted pair transmit function the differential driver circuitry in the txd and txp pins provides the necessary electrical driving capability and the pre-distortion control for transmitting signals over maximum length twisted pair cable, as specified by the 10base-t supplement to the ieee 802.3 stan- dard. the transmit function for data output meets the propagation delays and jitter specified by the standard. twisted pair receive function the receiver complies with the receiver specifications of the ieee 802.3 10base-t standard, including noise immunity and received signal rejection criteria ( ? smart squelch ? ). signals meeting these criteria appearing at the rxd differential input pair are routed to the mendec. the receiver function meets the propagation delays and jitter requirements specified by the stan- dard. the receiver squelch level drops to half its thresh- old value after unsquelch to allow reception of minimum amplitude signals and to offset carrier fade in the event of worst case signal attenuation conditions. note that the 10base-t standard defines the receive input amplitude at the external media dependent inter- face (mdi). filter and transformer loss are not speci- fied. the t-mau receiver squelch levels are designed to account for a 1 db insertion loss at 10 mhz for the type of receive filters and transformers usually used. normal 10base-t compatible receive thresholds are invoked when the lrt bit (csr15, bit 9) is low. when the lrt bit is set, the low receive threshold option is invoked, and the sensitivity of the t-mau receiver is increased. increasing t-mau sensitivity allows the use of lines longer than the 100 m target distance of stan- dard 10base-t (assuming typical 24 awg cable). increased receiver sensitivity compensates for the increased signal attenuation caused by the additional cable distance. however, making the receiver more sensitive means that it is also more susceptible to extraneous noise, pri- marily caused by coupling from co-resident services (crosstalk). for this reason, end users may wish to invoke the low receive threshold option on 4-pair cable only. multi-pair cables within the same outer sheath have lower crosstalk attenuation, and may allow noise emitted from adjacent pairs to couple into the receive pair, and be of sufficient amplitude to falsely unsquelch the t-mau. link test function the link test function is implemented as specified by 10base-t standard. during periods of transmit pair inactivity, ? link beat pulses ? will be periodically sent over the twisted pair medium to constantly monitor medium integrity.
78 am79c961a when the link test function is enabled (dlnktst bit in csr15 is cleared), the absence of link beat pulses and receive data on the rxd pair will cause the tmau to go into the link fail state. in the link fail state, data transmission, data reception, data loopback and the collision detection functions are disabled and remain disabled until valid data or greater than 5 consecutive link pulses appear on the rxd pair. during link fail, the link status (lnkst indicated by led0 ) signal is inactive. when the link is identified as functional, the lnkst signal is asserted, and led0 output will be activated. upon power up or assertion of the reset pin, the t-mau will be forced into the link fail state. reading the reset register of the pcnet-isa + (soft- ware reset) has no effect on the t-mau in order to inter-operate with systems which do not implement link test, this function can be disabled by setting the dlnktst bit. with link test disabled, the data driver, receiver and loopback functions as well as collision detection remain enabled irrespective of the presence or absence of data or link pulses on the rxd pair. link test pulses continue to be sent regard- less of the state of the dlnktst bit. polarity detection and reversal the t-mau receive function includes the ability to invert the polarity of the signals appearing at the rxd pair if the polarity of the received signal is reversed (such as in the case of a wiring error). this feature allows data packets received from a reverse wired rxd input pair to be corrected in the t-mau prior to transfer to the mendec. the polarity detection func- tion is activated following reset or link fail, and will reverse the receive polarity based on both the polarity of any previous link beat pulses and the polarity of sub- sequent packets with a valid end transmit delimiter (etd). when in the link fail state, the t-mau will recognize link beat pulses of either positive or negative polarity. exit from the link fail state occurs at the reception of 5 ? 6 consecutive link beat pulses of identical polarity. on entry to the link pass state, the polarity of the last 5 link beat pulses is used to determine the initial receive polarity configuration and the receiver is reconfigured to subsequently recognize only link beat pulses of the previously recognized polarity. positive link beat pulses are defined as transmitted sig- nal with a positive amplitude greater than 585 mv with a pulse width of 60 ns ? 200 ns. this positive excursion may be followed by a negative excursion. this defini- tion is consistent with the expected received signal at a correctly wired receiver, when a link beat pulse, which fits the template of figure 14-12 of the 10base-t stan- dard, is generated at a transmitter and passed through 100 m of twisted pair cable. negative link beat pulses are defined as transmitted signals with a negative amplitude greater than 585 mv with a pulse width of 60 ns ? 200 ns. this negative excursion may be followed by a positive excursion. this definition is consistent with the expected received sig- nal at a reverse wired receiver, when a link beat pulse which fits the template of figure 14-12 in the 10base-t standard is generated at a transmitter and passed through 100 m of twisted pair cable. the polarity detection/correction algorithm will remain ? armed ? until two consecutive packets with valid etd of identical polarity are detected. when ? armed, ? the receiver is capable of changing the initial or previous polarity configuration according to the detected etd polarity. on receipt of the first packet with valid etd following reset or link fail, the t-mau will use the inferred polarity information to configure its rxd input, regardless of its previous state. on receipt of a second packet with a valid etd with correct polarity, the detection/correction algorithm will ? lock-in ? the received polarity. if the sec- ond (or subsequent) packet is not detected as confirm- ing the previous polarity decision, the most recently detected etd polarity will be used as the default. note that packets with invalid etd have no effect on updat- ing the previous polarity decision. once two consecu- tive packets with valid etd have been received, the t-mau will lock the correction algorithm until either a link fail condition occurs or reset is asserted. during polarity reversal, an internal pol signal will be active. during normal polarity conditions, this internal pol signal is inactive. the state of this signal can be read by software and/or displayed by led when enabled by the led control bits in the isa bus config- uration registers (isacsr5, 6, 7). twisted pair interface status three internal signals (xmt, rcv and col) indicate whether the t-mau is transmitting, receiving, or in a collision state. these signals are internal signals and the behavior of the led outputs depends on how the led output circuitry is programmed. the t-mau will power up in the link fail state and the normal algorithm will apply to allow it to enter the link pass state. in the link pass state, transmit or receive activity will be indicated by assertion of rcv signal going active. if t-mau is selected using the portsel bits in csr15, when moving from aui to t-mau selec- tion, the t-mau will be forced into the link fail state. in the link fail state, xmt, rcv and col are inactive. collision detect function activity on both twisted pair signals rxd and txd constitutes a collision, thereby causing the col signal to be asserted. (col is used by the led control cir- cuits) col will remain asserted until one of the two col-
am79c961a 79 liding signals changes from active to idle. col stays active for 2 bit times at the end of a collision. signal quality error (sqe) test (heartbeat) function the sqe function is disabled when the 10base-t port is selected and in link fail state. jabber function the jabber function inhibits the twisted pair transmit function of the t-mau if the txd circuit is active for an excessive period (20 ms ? 150 ms). this prevents any one node from disrupting the network due to a ? stuck-on ? or faulty transmitter. if this maximum transmit time is exceeded, the t-mau transmitter circuitry is dis- abled, the jab bit is set (csr4, bit 1), and the col sig- nal asserted. once the transmit data stream to the t-mau is removed, an ? unjab ? time of 250 ms ? 750 ms will elapse before the t-mau deasserts col and re-enables the transmit circuitry. power down the t-mau circuitry can be made to go into low power mode. this feature is useful in battery powered or low duty cycle systems. the t-mau will go into power down mode when reset is active, coma mode is ac- tive, or the t-mau is not selected. refer to the power down mode section for a description of the various power down modes. any of the three conditions listed above resets the internal logic of the t-mau and places the device into power down mode. in this mode, the twisted pair driver pins (txd ,txp ) are asserted low, and the in- ternal t-mau status signals (lnkst, rcvpol, xmt, rcv and collision) are inactive. once the sleep pin is deasserted, the t-mau will be forced into the link fail state. the t-mau will move to the link pass state only after 5 ? 6 link beat pulses and/ or a single received message is detected on the rxd pair. in snooze mode, the t-mau receive circuitry will remain enabled even while the sleep pin is driven low. the t-mau circuitry will always go into power down mode if reset is asserted, coma is enabled, or the t-mau is not selected. full duplex operation the pcnet-isa ii supports full duplex operation on the 10base-t, aui, and gpsi ports. full duplex operation allows simultaneous transmit and receive activity on the txd and rxd pairs of the 10base-t port, the do and di pairs of the aui port, and the txdat and rxdat pins of the gpsi port. it is enabled by the fden and auifd bits located in isacsr9. when op- erating in the full duplex mode, the following changes to device operation are made: bus interface/buffer management unit changes: 1. the first 64 bytes of every transmit frame are not preserved in the transmit fifo during transmission of the first 512 bits transmitted on the network, as described in the transmit exception conditions section. instead, when full duplex mode is active and a frame is being transmitted, the xmtfw bits (csr80, bits 9, 8) always govern when transmit dma is requested. 2. successful reception of the first 64 bytes of every receive frame is not a requirement for receive dma to begin as described in the receive exception conditions section. instead, receive dma will be requested as soon as either the rcvfw threshold (csr80 bits 12, 13) is reached or a complete valid receive frame is in the receive fifo, regardless of length. this receive fifo operation is identical to when the rpa bit (csr124, bit 3) is set during half duplex mode operation. mac engine changes: 1. changes to the transmit deferral mechanism: a. transmission is not deferred while receive is active. b. the inter packet gap (ipg) counter which gov- erns transmit deferral during the ipg between back-to-back transmits is started when transmit activity for the first packet ends instead of when transmit and carrier activity ends. 2. when the aui or gpsi port is active, loss of carrier (lcar) reporting is disabled (lcar is still reported when the 10base-t port is active if a packet is transmitted while in the link fail state). 3. the 4.0 s carrier sense blinding period after a transmission during which the sqe test normally occurs is disabled. 4. when the aui or gpsi port is active, the sqe test error (collision error, cerr) reporting is disabled (cerr is still reported when the 10base-t port is active if a packet is transmitted while in the link fail state). 5. the collision indication input to the mac engine is ignored. t-mau changes: 1. the transmit to receive loopback path in the t-mau is disabled. 2. the collision detect circuit is disabled. 3. the ? heartbeat ? generation (sqe test function) is disabled.
80 am79c961a eadi (external address detection interface) this interface is provided to allow external address fil- tering. it is selected by setting the eadisel bit in isacsr2. this feature is typically utilized for terminal servers, bridges and/or router type products. the use of external logic is required to capture the serial bit stream from the pcnet-isa ii controller, compare it with a table of stored addresses or identifiers, and perform the desired function. the eadi interface operates directly from the nrz decoded data and clock recovered by the manchester decoder or input to the gpsi, allowing the external address detection to be performed in parallel with frame reception and address comparison in the mac station address detection (sad) block. srdclk is provided to allow clocking of the receive bit stream into the external address detection logic. srdclk runs only during frame reception activity. once a received frame commences and data and clock are available, the eadi logic will monitor the alternating ( ? 1,0") preamble pattern until the two ones of the start frame delimiter ( ? 1,0,1,0,1,0,1,1") are detected, at which point the sf/bd output will be driven high. after sf/bd is asserted the serial data from srd should be de-serialized and sent to a content address- able memory (cam) or other address detection device. to allow simple serial to parallel conversion, sf/bd is provided as a strobe and/or marker to indicate the delineation of bytes, subsequent to the sfd. this pro- vides a mechanism to allow not only capture and/or de- coding of the physical or logical (group) address, it also facilitates the capture of header information to determine protocol and or inter-networking information. the ear pin is driven low by the external address comparison logic to reject the frame. if an internal address match is detected by comparison with either the physical or logical address field, the frame will be accepted regardless of the condition of ear . incoming frames which do not pass the internal address comparison will continue to be received. this allows approximately 58 byte times after the last desti- nation address bit is available to generate the ear signal, assuming the device is not configured to accept runt packets. ear will be ignored after 64 byte times after the sfd, and the frame will be accepted if ear has not been asserted before this time. if runt packet accept is configured, the ear signal must be generated prior to the receive message completion, which could be as short as 12 byte times (assuming 6 bytes for source address, 2 bytes for length, no data, 4 bytes for fcs) after the last bit of the destination address is available. ear must have a pulse width of at least 200 ns. note that setting the prom bit (csr15, bit 15) will cause all receive frames to be received, regardless of the state of the ear input. if the drcupa bit (csr15.b) is set and the logical address (ladrf) is set to zero, only frames which are not rejected by ear will be received. the eadi interface will operate as long as the strt bit in csr0 is set, even if the receiver and/or transmitter are disabled by software (dtx and drx bits in csr15 set). this situation is useful as a power down mode in that the pcnet-isa ii controller will not perform any dma operations; this saves power by not utilizing the isa bus driver circuits. however, external circuitry could still respond to specific frames on the network to facilitate remote node control. the table below summarizes the operation of the eadi features. internal/external address recognition capabilities general purpose serial interface (gpsi) the pcnet-isa ii controller contains a general purpose serial interface (gpsi) designed for testing the digital portions of the chip. the mendec, aui, and twisted pair interface are by-passed once the device is set up in the special ? test mode ? for accessing the gpsi functions. although this access is intended only for testing the device, some users may find the non-en- coded data functions useful in some special applications. note, however, that the gpsi functions can be accessed only when the pcnet-isa ii devices operate as a bus master. the pcnet-isa ii gpsi signals are consistent with the lance digital serial interface. since the gpsi func- tions can be accessed only through a special test mode, expect some loss of functionality to the device when the gpsi is invoked. the aui and 10base-t analog interfaces are disabled along with the internal prom ear required timing received messages 1 x no timing requirements all received frames 0 1 no timing requirements all received frames 0 0 low for 200 ns within 512 bits after sfd physical/logical matches
am79c961a 81 mendec logic. the la (unlatched address) pins are removed and become the gpsi signals, therefore, only 20 bits of address space is available. the table below shows the gpsi pin configuration: to invoke the gpsi signals, follow the procedure below: 1. after reset or i/o read of reset address, write 10b to portsel bits in csr15. 2. set the entst bit in csr4 3. set the gpsien bit in csr124 (see note below) (the pins la17 ? la23 will change function after the completion of the above three steps.) 4. clear the entst bit in csr4 5. clear media select bits in isacsr2 6. define the portsel bits in the mode register (csr15) to be 10b to define gpsi port. the mode register image is in the initialization block. note: la pins will be tristated before writing to gpsien bit. after writing to gpsien, la[17 ? 21] will be inputs, la[22 ? 23] will be outputs. gpsi pin configurations note: the gpsi function is available only in the bus master mode of operation. gpsi function gpsi i/o type lance gpsi pin pcnet-isa ii gpsi pin pcnet-isa ii pin number pcnet-isa ii normal pin function receive data i rx rxdat 5 la17 receive clock i rclk srdclk 6 la18 receive carrier sense i rena rxcrs 7 la19 collision i clsn clsn 9 la20 transmit clock i tclk stdclk 10 la21 transmit enable o tena txen 11 la22 transmit data o tx txdat 12 la23
82 am79c961a ieee 1149.1 test access port interface an ieee 1149.1 compatible boundary scan test access port is provided for board-level continuity test and diag- nostics. all digital input, output, and input/output pins are tested. analog pins, including the aui differential driver (do ) and receivers (di , ci ), and the crystal input (xtal1/xtal2) pins, are tested. the t-mau drivers txd , txp , and receiver rxd are also tested. the following is a brief summary of the ieee 1149.1 compatible test functions implemented in the pc- net-isa ii controller. boundary scan circuit the boundary scan test circuit requires four extra pins (tck, tms, tdi and tdo), defined as the test access port (tap). it includes a finite state machine (fsm), an instruction register, a data register array, and a power-on reset circuit. internal pull-up resistors are provided for the tdi, tck, and tms pins. the tck pin must not be left unconnected. the boundary scan cir- cuit remains active during sleep. tap fsm the tap engine is a 16-state fsm, driven by the test clock (tck) and the test mode select (tms) pins. this fsm is in its reset state at power-up or reset. an independent power-on reset circuit is provided to ensure the fsm is in the test_logic_reset state at power-up. supported instructions in addition to the minimum ieee 1149.1 requirements (bypass, extest and sample instructions), three additional instructions (idcode, tribyp and setbyp) are provided to further ease board-level testing. all unused instruction codes are reserved. see the table below for a summary of supported instructions. instruction register and decoding logic after hardware or software reset, the idcode instruction is always invoked. the decoding logic gives signals to control the data flow in the data registers according to the current instruction. boundary scan register (bsr) each bsr cell has two stages. a flip-flop and a latch are used in the serial shift stage and the parallel output stage, respectively. there are four possible operational modes in the bsr cell: other data registers (1) bypass reg (1 bit) (2) dev id reg (32 bits) ieee 1149.1 supported instruction summary power saving modes the pcnet-isa ii controller supports two hardware power-savings modes. both are entered by asserting the sleep pin low. in coma mode, the pcnet-isa ii controller will go into deep sleep with no support to automatically wake itself up. sleep mode is enabled when the awake bit in isacsr2 is reset. this mode is the default powerdown mode. in snooze mode, enabled by setting the awake bit in isacsr2 and driving the sleep pin low, the t-mau receive circuitry will remain enabled even while the sleep pin is driven low. the led0 output will also continue to function, indicating a good 10base-t link if 1capture 2shift 3 update 4 system function bits 31 ? 28: version bits 27 ? 12: part number (2261h) bits 11 ? 1: manufacturer id. the 11 bit manufacturer id code for amd is 00000000001 according to jedec publication 106-a. bit 0: always a logic 1 instruction name description selected data reg mode instruction code extest external test bsr test 0000 idcode id code inspection id reg normal 0001 sample sample boundary bsr normal 0010 tribyp force tristate bypass normal 0011 setbyp control boundary to 1/0 bypass test 0100 bypass bypass scan bypass normal 1111
am79c961a 83 there are link beat pulses or valid frames present. this led0 pin can be used to drive a led and/or external hardware that directly controls the sleep pin of the pcnet-isa ii controller. this configuration effectively wakes the system when there is any activity on the 10base-t link. access operations (software) we begin by describing how byte and word data are addressed on the isa bus, including conversion cycles where 16-bit accesses are turned into 8-bit accesses because the resource accessed did not support 16-bit operations. then we describe how registers and other resources are accessed. this section is for the device programmer, while the next section (bus cycles) is for the hardware designer. i/o resources the pcnet-isa ii controller has both i/o and memory resources. in the i/o space the resources are orga- nized as indicated in the following table: the pcnet-isa ii controller does not respond to any addresses outside of the offset range 0-17h. i/o offsets 18h and up are not used by the pcnet-isa ii controller. i/o register access the register address port (rap) is shared by the regis- ter data port (rdp) and the isacsr data port (idp) to save registers. to access the ethernet controller ? s rdp or idp, the rap should be written first, followed by the read or write access to the rdp or idp. i/o register accesses should be coded as 16-bit accesses, even if the pcnet-isa ii controller is hardware configured for 8-bit i/o bus cycles. it is acceptable (and transparent) for the motherboard to turn a 16-bit software access into two separate 8-bit hardware bus cycles. the moth- erboard accesses the low byte before the high byte and the pcnet-isa ii controller has circuitry to specifically support this type of access. the reset register causes a reset when read. any value will be accepted and the cycle may be 8 or 16 bits wide. writes are ignored. all pcnet-isa ii controller register accesses should be coded as 16-bit operations. ? note that the rap is cleared on reset. ? ieee address access the address prom may be an external memory device that contains the node ? s unique physical ether- net address and any other data stored by the board manufacturer. the software accesses must be 16-bit. this information may be stored in the eeprom. boot prom access the boot prom is an external memory resource located by the address selected by the eeprom or the bpam input in slave mode. it may be software accessed as an 8-bit or 16-bit resource but the latter is recommended for best performance. static ram access the static ram is only present in the bus slave mode. in the bus slave mode, two sram access schemes are available. when the shared memory architecture mode is selected, the sram is accessed using isa memory cycles to the address range selected by the smam input. it may be accessed as an 8 or 16-bit resource but the latter is recommended for best perfor- mance. when the programmed i/o architecture mode is selected, the sram is accessed through isacsr0 and isacsr1 using the rap and idp. bus cycles (hardware) the pcnet-isa ii controller supports both 8-bit and 16-bit hardware bus cycles. the following sections out- line where any limitations apply based upon the archi- tecture mode and/or the resource that is being accessed (pcnet-isa ii controller registers, address prom, boot prom, or shared memory sram). for completeness, the following sections are arranged by architecture (bus master mode or bus slave mode). sram resources apply only to bus slave mode. all resources (registers, proms, sram) are pre- sented to the isa bus by the pcnet-isa ii controller. with few exceptions, these resources can be config- ured for either 8-bit or 16-bit bus cycles. the i/o resources (registers, address prom) are width con- figured using the eeprom. the memory resources (boot prom, sram) are width configured by external hardware. for 16-bit memory accesses, hardware external to the pcnet-isa ii controller asserts memcs16 when either of the two memory resources is selected. the isa bus requires that all memory resources within a block of 128 kbytes be the same width, either 8- or 16-bits. the reason for this is that the memcs16 signal is generally a decode of the la 17-23 address lines. 16-bit memory capability is desirable since two 8-bit accesses take the same amount of time as four 16-bit accesses. all accesses to 8-bit resources (which do not return memcs16 or iocs16 ) use sd0-7. if an odd byte is accessed, the current master swap buffer turns on. offset #bytes register 0h 16 ieee address 10h 2 rdp 12h 2 rap(shared by rdp and idp) 14h 2 reset 16h 2 idp
84 am79c961a during an odd byte read the swap buffer copies the data from sd0-7 to the high byte. during an odd byte write the current master swap buffer copies the data from the high byte to sd0-7. the pcnet-isa ii control- ler can be configured to be an 8-bit i/o resource even in a 16-bit system; this is set by the eeprom. it is rec- ommended that the pcnet-isa ii controller be config- ured for 8-bit only i/o bus cycles for maximum compatibility with pc/at clone motherboards. when the pcnet-isa ii controller is in an 8-bit system such as a pc/xt, sbhe and iocs16 must be left unconnected (these signals do not exist in the pc/xt). this will force all resources (i/o and memory) to sup- port only 8-bit bus cycles. the pcnet-isa ii controller will function in an 8-bit system only if configured for bus slave mode. accesses to 16-bit resources (which do return memcs16 or iocs16 ) use either or both sd0 ? 7 and sd8 ? 15. a word access is indicated by a0=0 and sbhe =0 and data is transferred on all 16 data lines. an even byte access is indicated by a0=0 and sbhe =1 and data is transferred on sd0 ? 7. an odd-byte access is indicated by a0=1 and sbhe =0 and data is trans- ferred on sd8-15. it is illegal to have a0=1 and sbhe =1 in any bus cycle. the pcnet-isa ii controller returns only iocs16 ; memcs16 must be generated by external hardware if desired. the use of memcs16 applies only to shared memory mode. the following table describes all possible types of isa bus accesses, including permanent master as current master and pcnet-isa ii controller as current master. the pcnet-isa ii controller will not work with 8-bit memory while it is current master. any descriptions of 8-bit memory accesses are for when the permanent master is current master . the two byte columns (d0 ? 7 and d8 ? 15) indicate whether the bus master or slave is driving the byte. cs16 is a shorthand for memcs16 and iocs16 . bus master mode the pcnet-isa ii controller can be configured as a bus master only in systems that support bus mastering. in addition, the system is assumed to support 16-bit memory (dma) cycles (the pcnet-isa ii controller does not use the memcs16 signal on the isa bus). this does not preclude the pcnet-isa ii controller from doing 8-bit i/o transfers. the pcnet-isa ii controller will not function as a bus master in 8-bit platforms such as the pc/xt. refresh cycles although the pcnet-isa ii controller is neither an origi- nator or a receiver of refresh cycles, it does need to avoid unintentional activity during a refresh cycle in bus master mode. a refresh cycle is performed as follows: first, the ref signal goes active. then a valid refresh address is placed on the address bus. memr goes ac- tive, the refresh is performed, and memr goes inac- tive. the refresh address is held for a short time and them goes invalid. finally, ref goes inactive. during a refresh cycle, as indicated by ref being active, the pcnet-isa ii controller ignores dack if it goes active until it goes inactive. it is necessary to ignore dack during a refresh because some motherboards gener- ate a false dack at that time. isa bus accesses address prom cycles external prom the address prom is a small (16 bytes) 8-bit prom connected to the pcnet-isa ii controller private data bus. the pcnet-isa ii controller will support only 8-bit isa i/o bus cycles for the address prom; this limita- tion is transparent to software and does not preclude 16-bit software i/o accesses. an access cycle begins r/w a0 sbhe cs16 d0 ? 7d8 ? 15 comments rd 0 1 x slave float low byte rd rd101slave float high byte rd with swap rd 0 0 1 slave float 16-bit rd converted to low byte rd rd 1 0 0 float slave high byte rd rd 0 0 0 slave slave 16-bit rd wr 0 1 x master float low byte wr wr 1 0 1 master float high byte wr with swap wr 0 0 1 master master 16-bit wr converted to low byte wr wr 1 0 0 float master high byte wr wr 0 0 0 master master 16-bit wr
am79c961a 85 with the permanent master driving aen low, driving the addressess valid, and driving ior active. the pcnet-isa ii controller detects this combination of sig- nals and arbitrates for the private data bus (prdb) if necessary. iochrdy is driven low during accesses to the address prom. when the private data bus becomes available, the pcnet-isa ii controller drives apcs active, releases iochrdy, turns on the data path from prd0-7, and enables the sd0-7 drivers (but not sd8-15). during this bus cycle, iocs16 is not driven active. this condi- tion is maintained until ior goes inactive, at which time the bus cycle ends. data is removed from sd0-7 within 30 ns. address prom cycles using eeprom data default mode. in this mode, the ieee address informa- tion is stored not in an external parallel prom but in the eeprom along with other configuration information. pcnet-isa ii will respond to i/o reads from the ieee address (the first 16 bytes of the i/o map) by supplying data from an internal ram inside pcnet-isa ii. this in- ternal ram is loaded with the ieee address at reset and is write protected. ethernet controller register cycles ethernet controller registers (rap, rdp, idp) are natu- rally 16-bit resources but can be configured to operate with 8-bit bus cycles provided the proper protocol is fol- lowed. this means on a read, the pcnet-isa ii control- ler will only drive the low byte of the system data bus; if an odd byte is accessed, it will be swapped down. the high byte of the system data bus is never driven by the pcnet-isa ii controller under these conditions. on a write cycle, the even byte is placed in a holding register. an odd byte write is internally swapped up and aug- mented with the even byte in the holding register to pro- vide an internal 16-bit write. this allows the use of 8-bit i/o bus cycles which are more likely to be compatible with all isa-compatible clones, but requires that both bytes be written in immediate succession. this is accomplished simply by treating the pcnet-isa ii con- troller registers as 16-bit software resources. the motherboard will convert the 16-bit accesses done by software into two sequential 8-bit accesses, an even byte access followed immediately by an odd byte access. an access cycle begins with the permanent master driving aen low, driving the address valid, and driving ior or iow active. the pcnet-isa ii controller detects this combination of signals and drives iochrdy low. iocs16 will also be driven low if 16-bit i/o bus cycles are enabled. when the register data is ready, iochrdy will be released high. this condition is maintained until ior or iow goes inactive, at which time the bus cycle ends. reset cycles a read to the reset address causes an pcnet-isa ii controller reset. this has the same effect as asserting the reset pin on the pcnet-isa + controller (which happens on system power up or on a hard boot) except that the t-mau is not reset. the t-mau will retain its link pass/fail state, disregarding the software reset command. the subsequent write cycle needed in the ne2100 lance based family of ethernet cards is not required but does not have any harmful effects. iocs16 is not asserted in this cycle. isa configuration register cycles the isa configuration registers are accessed by plac- ing the address of the desired register into the rap and reading the idp. the isacsr bus cycles are identical to all other pcnet-isa ii controller register bus cycles. boot prom cycles the boot prom is an 8-bit prom connected to the pcnet-isa ii controller private data bus (prdb) and can occupy up to 64k of address space. since the pc- net-isa ii controller does not generate memcs16 , only 8-bit isa memory bus cycles to the boot prom are supported in bus master mode; this limitation is trans- parent to software and does not preclude 16-bit soft- ware memory accesses. a boot prom access cycle begins with the permanent master driving the addresses valid, ref inactive, and memr active. (aen is not involved in memory cycles). the pcnet-isa ii controller detects this combination of signals, drives iochrdy low, and reads a byte out of the boot prom. the data byte read is driven onto the lower sys- tem data bus lines and iochrdy is released. this condition is maintained until memr goes inactive, at which time the access cycle ends. the bpcs signal generated by the pcnet-isa ii con- troller is three 20 mhz clock cycles wide (300 ns). including delays, the boot prom has 275 ns to respond to the bpcs signal from the pcnet-isa ii con- troller. this signal is intended to be connected to the cs pin on the boot prom, with the prom oe pin tied to ground. current master operation current master operation only occurs in the bus master mode. it does not occur in the bus slave mode. there are three phases to the use of the bus by the pc- net-isa ii controller as current master, the obtain phase, the access phase, and the release phase. obtain phase a master mode transfer cycle begins by asserting drq. when the permanent master asserts dack , the pcnet-isa ii controller asserts master , signifying it has taken control of the isa bus. the permanent mas- ter tristates the address, command, and data lines
86 am79c961a within 60 ns of dack going active. the permanent master drives aen inactive within 71 ns of master going active. access phase the isa bus requires a wait of at least 125 ns after master is asserted before the new master is allowed to drive the address, command, and data lines. the pcnet-isa ii controller will actually wait 3 clock cycles or 150 ns. the following signals are not driven by the permanent master and are simply pulled high: bale, iochrdy, iocs16 , memcs16 , srdy . therefore, the pcnet-isa ii controller assumes the memory which it is accessing is 16 bits wide and can complete an access in the time programmed for the pcnet-isa ii controller memr and memw signals. refer to the isa bus configuration register description section. release phase when the pcnet-isa ii controller is finished with the bus, it drives the command lines inactive. 50 ns later, the controller tri-states the command, address, and data lines and drives drq inactive. 50 ns later, the con- troller drives master inactive. the permanent master drives aen active within 71 ns of master going inactive. the permanent master is allowed to drive the command lines no sooner than 60 ns after dack goes inactive. master mode memory read cycle after the pcnet-isa ii controller has acquired the isa bus, it can perform a memory read cycle. all timing is generated relative to the 20 mhz clock (network clock). since there is no way to tell if memory is 8-bit or 16-bit or when it is ready, the pcnet-isa ii controller by default assumes 16-bit, 1 wait state memory. the wait state assumption is based on the default value in the msrda register in isacsr0. the cycle begins with sa0-19, sbhe , and la17-23 being presented. the isa bus requires them to be valid for at least 28 ns before a read command and the pc- net-isa ii controller provides one clock or 50 ns of setup time before asserting memr . the isa bus requires memr to be active for at least 219 ns, and the pcnet-isa ii controller provides a default of 5 clocks, or 250 ns, but this can be tuned for faster systems with the master mode read active (msrda) register (see section 2.5.2). also, if iochrdy is driven low, the pcnet-isa ii controller will wait. the wait state counter must expire and iochrdy must be high for the pcnet-isa ii controller to continue. the pcnet-isa ii controller then accepts the memory read data. the isa bus requires all command lines to remain inactive for at least 97 ns before starting another bus cycle and the pcnet-isa ii controller pro- vides at least two clocks or 100 ns of inactive time. the isa bus requires read data to be valid no more than 173 ns after receiving memr active and the pc- net-isa ii controller requires 10 ns of data setup time. the isa bus requires read data to provide at least 0 ns of hold time and to be removed from the bus within 30 ns after memr goes inactive. the pcnet-isa ii control- ler requires 0 ns of data hold time. master mode memory write cycle after the pcnet-isa ii controller has acquired the isa bus, it can perform a memory write cycle. all timing is generated relative to a 20 mhz clock which happens to be the same as the network clock. since there is no way to tell if memory is 8- or 16-bit or when it is ready, the pcnet-isa ii controller by default assumes 16-bit, 1 wait state memory. the wait state assumption is based on the default value in the mswra register in isacsr1. the cycle begins with sa0-19, sbhe , and la17-23 being presented. the isa bus requires them to be valid at least 28 ns before memw goes active and data to be valid at least 22 ns before memw goes active. the pc- net-isa ii controller provides one clock or 50 ns of setup time for all these signals. the isa bus requires memw to be active for at least 219 ns, and the pcnet-isa ii controller provides a default of 5 clocks, or 250 ns, but this can be tuned for faster systems with the master mode write active (mswra) register (isacsr1). also, if iochrdy is driven low, the pcnet-isa ii controller will wait. iochrdy must be high for the pcnet-isa ii controller to continue. the isa bus requires data to be valid for at least 25 ns after memw goes inactive, and the pcnet-isa ii con- troller provides one clock or 50 ns. the isa bus requires all command lines to remain inactive for at least 97 ns before starting another bus cycle. the pcnet-isa ii controller provides at least two clocks or 100 ns of inactive time when bit 4 in isacsr2 is set. the eisa bus requires all command lines to remain inactive for at least 170 ns before starting another bus cycle. when bit 4 in isacsr4 is cleared, the pcnet-isa ii controller provides 200 ns of inactive time. back-to-back dma requests the pcnet-isa ii provides for fair bus bandwidth shar- ing between two bus mastering devices on the isa bus through an adaptive delay which is inserted between back-to-back dma requests. when the pcnet-isa ii requires bus access immedi- ately following a bus ownership period, it first checks the status of the three currently unused drq pins. if a
am79c961a 87 lower priority drq pin than the one currently being used by the pcnet-isa ii is asserted, the pcnet-isa ii will wait 2.6 s after the deassertion of dack before re-asserting its drq pin. if no lower priority drq pin is asserted, the pcnet-isa ii may re-assert its drq pin after as short as 1.1 s following dack deassertion. the priorities assumed by the pcnet-isa ii are ordered drq3, drq5, drq6, drq7, with drq3 having high- est priority and drq7 having the lowest priority. this priority ordering matches that used by typical isa bus dma controllers. this adaptive delay scheme allows for fair bus band- width sharing when two bus mastering devices, e.g. two pcnet-isa ii devices, are on an isa bus. the con- troller using the higher priority dma channel cannot lock out the controller using the lower priority dma channel because of the 2.6 s delay that is inserted before drq reassertion when a lower priority drq pin is asserted. when there is no lower priority dma request asserted, the pcnet-isa ii re-requests the bus immediately, providing optimal performance when there is no competition for bus access. bus slave mode the pcnet-isa ii can be configured to be a bus slave for systems that do not support bus mastering or require a local memory to tolerate high bus latencies. in the bus slave mode, the i/o map of the pcnet-isa ii is identical to the i/o map when in the bus master mode (see i/o resources section). hence, the address prom, controller registers, and reset port are accessed through i/o cycles on the isa bus. however, the initialization block, descriptor rings, and buffers, which are located in system memory when in the bus master mode, are located in a local sram when in the bus slave mode. the local sram can be accessed by memory cycles on the isa bus (shared memory archi- tecture) or by i/o cycles on the isa bus (programmed i/o mode). address prom cycles external prom the address prom is a small (16 bytes) 8-bit prom connected to the pcnet-isa ii controller private data bus (prdb). the pcnet-isa ii controller will support only 8-bit isa i/o bus cycles for the address prom; this limitation is transparent to software and does not preclude 16-bit software i/o accesses. an access cycle begins with the permanent master driving aen low, driving the addresses valid, and driving ior active. the pcnet-isa ii controller detects this combination of sig- nals and arbitrates for the private data bus if neces- sary. iochrdy is always driven low during address prom accesses. when the private data bus becomes available, the pcnet-isa ii controller drives apcs active, releases iochrdy, turns on the data path from prd0-7, and enables the sd0-7 drivers (but not sd8-15). during this bus cycle, iocs16 is not driven active. this condi- tion is maintained until ior goes inactive, at which time the access cycle ends. data is removed from sd0-7 within 30 ns. the pcnet-isa ii controller will perform 8-bit isa bus cycle operation for all resources (registers, proms, sram) if sbhe has been left unconnected, such as in the case of an 8-bit system like the pc/xt. ethernet controller register cycles ethernet controller registers (rap, rdp, isacsr) are naturally 16-bit resources but can be configured to operate with 8-bit bus cycles provided the proper pro- tocol is followed. this is programmable by the eeprom. this means on a read, the pcnet-isa ii con- troller will only drive the low byte of the system data bus; if an odd byte is accessed, it will be swapped down. the high byte of the system data bus is never driven by the pcnet-isa ii controller under these con- ditions. on a write, the even byte is placed in a holding register. an odd-byte write is internally swapped up and augmented with the even byte in the holding register to provide an internal 16-bit write. this allows the use of 8-bit i/o bus cycles which are more likely to be compat- ible with all clones, but requires that both bytes be writ- ten in immediate succession. this is accomplished simply by treating the pcnet-isa ii controller controller registers as 16-bit software resources. the mother- board will convert the 16-bit accesses done by soft- ware into two sequential 8-bit accesses, an even-byte access followed immediately by an odd-byte access. an access cycle begins with the permanent master driving aen low, driving the address valid, and driv- ing ior or iow active. the pcnet-isa ii controller de- tects this combination of signals and drives iochrdy low. iocs16 will also be driven low if 16-bit i/o bus cycles are enabled. when the register data is ready, iochrdy will be released high. this condition is maintained until ior or iow goes inactive, at which time the bus cycle ends. the pcnet-isa ii controller will perform 8-bit isa bus cycle operation for all resources (registers, proms, sram) if sbhe has been left unconnected, such as in the case of an 8-bit system like the pc/xt. reset cycles a read to the reset address causes an pcnet-isa ii controller reset. this has the same effect as asserting the reset pin on the pcnet-isa + controller (which happens on system power up or on a hard boot) except that the t-mau is not reset. the t-mau will retain its link pass/fail state, disregarding the software reset command. the subsequent write cycle needed in the ne2100 lance- based family of ethernet cards is not required but does not have any harmful effects. iocs16 is not asserted in this cycle.
88 am79c961a isa configuration register cycles the isa configuration register is accessed by placing the address of the desired register into the rap and reading the idp. the isacsr bus cycles are identical to all other pcnet-isa ii controller register bus cycles. boot prom cycles the boot prom is an 8-bit prom connected to the pcnet-isa ii controller private data bus (prdb), and can occupy up to 64 kbytes of address space. in shared memory mode, an external address compara- tor is responsible for asserting bpam to the pcnet-isa ii controller. bpam is intended to be a perfect decode of the boot prom address space, i.e. la17-23, sa16. the la bus must be latched with bale in order to pro- vide stable signal for bpam . ref inactive must be used by the external logic to gate boot prom address decoding. this same logic must assert memcs16 to the isa bus if 16-bit boot prom bus cycles are desired. in the bus slave mode, boot prom cycles can be pro- grammed to be 8 or 16-bit isa memory cycles with the bp_16b bit (pnp 0x42). if the bp_16b bit is set, the pcnet-isa ii assumes 16-bit isa memory cycles for the boot prom. in this case, the external hardware responsible for generating bpam must also generate memcs16 . a 16-bit boot prom bus cycle begins with the permanent master driving the addresses valid and memr active. (aen is not involved in memory cycles). external hardware would assert bpam and memcs16 . the pcnet-isa ii controller detects this combination of signals, drives iochrdy low, and reads two bytes out of the boot prom. the data bytes read from the prom are driven by the pcnet-isa ii controller onto sd0-15 and iochrdy is released. this condition is maintained until memr goes inactive, at which time the access cycle ends. the pcnet-isa ii controller will perform 8-bit isa bus cycle operation for all resource (registers, proms, sram) if sbhe has been left unconnected, such as in the case of an 8-bit system like the pc/xt. the bpcs signal generated by the pcnet-isa ii con- troller is three 20 mhz clock cycles wide (350 ns). including delays, the boot prom has 275 ns to respond to the bpcs signal from the pcnet-isa ii con- troller. this signal is intended to be connected to the cs pin on the boot prom, with the prom oe pin tied to ground. static ram cycles ? shared memory architecture in the shared memory architecture mode, the sram is an 8-bit device connected to the pcnet-isa ii controller private bus, and can occupy up to 64 kbytes of address space. the sram is memory mapped into the isa memory space at an address range determined by external decode logic. the external address compara- tor is responsible for asserting smam to the pcnet-isa ii controller. smam is intended to be a perfect decode of the sram address space, i.e. la17-23, sa16 for 64 kbytes of sram. the la signals must be latched by bale in order to provide a stable decode for smam . the pcnet-isa ii controller assumes 16-bit isa mem- ory bus cycles for the sram, so this same logic must assert memcs16 to the isa bus if 16-bit bus cycles are to be supported. a 16-bit sram bus cycle begins with the permanent master driving the addresses valid, ref inactive, and either memr or memw active. (aen is not involved in memory cycles). external hardware would assert smam and memcs16 . the pcnet-isa ii controller detects this combination of signals and initiates the sram access. in a write cycle, the pcnet-isa ii controller stores the data into an internal holding register, allowing the isa bus cycle to finish normally. the data in the holding reg- ister will then be written to the sram without the need for isa bus control. in the event the holding register is already filled with unwritten sram data, the pcnet-isa ii controller will extend the isa write cycle by driving iochrdy low until the unwritten data is stored in the sram. the current isa bus cycle will then complete normally. in a read cycle, the pcnet-isa ii controller arbitrates for the private bus. if it is unavailable, the pcnet-isa ii controller drives iochrdy low. the pcnet-isa ii controller compares the 16 bits of address on the sys- tem address bus with that of a data word held in an internal pre-fetch register. if the address does not match that of the prefetched sram data, then the pcnet-isa ii controller drives iochrdy low and reads two bytes from the sram. the pcnet-isa ii controller then proceeds as though the addressed data location had been prefetched. if the internal prefetch buffer contains the correct data, then the pre-fetch buffer data is driven on the system data bus. if iochrdy was previously driven low due to either private data bus arbitration or sram access, then it is released high. the pcnet-isa ii controller remains in this state until memr is de-asserted, at which time the pcnet-isa ii controller performs a new prefetch of the sram. in this way memory read wait states can be minimized. the pcnet-isa ii controller performs prefetches of the sram between isa bus cycles. the sram is prefetched in an incrementing word address fashion. prefetched data are invalidated by any other activity on the private bus, including shared memory writes by either the isa bus or the network interface, and also address and boot prom reads.
am79c961a 89 the only way to configure the pcnet-isa ii controller for 8-bit isa bus cycles for sram accesses is to con- figure the entire pcnet-isa ii controller to support only 8-bit isa bus cycles. this is accomplished by leaving the sbhe pin disconnected. the pcnet-isa ii control- ler will perform 8-bit isa bus cycle operation for all resources (registers, proms, sram) if sbhe has never been driven active since the last reset, such as in the case of an 8-bit system like the pc/xt. in this case, the external address decode logic must not assert memcs16 to the isa bus, which will be the case if memcs16 is left unconnected. it is possible to man- ufacture a dual 8/16 bit pcnet-isa ii controller adapter card, as the memcs16 and sbhe signals do not exist in the pc/xt environment. at the memory device level, each sram private bus read cycle takes two 50 ns clock periods for a maxi- mum read access time of 75 ns. the timing looks like this: the address and sroe go active within 20 ns of the clock going high. data is required to be valid 5 ns before the end of the second clock cycle. address and sroe have a 0 ns hold time after the end of the second clock cycle. note that the pcnet-isa ii controller does not normally provide a separate sram cs signal; sram cs must always be asserted. sram private bus write cycles require three 50 ns clock periods to guarantee non-negative address setup and hold times with regard to srwe . the timing is illustrated as follows: address and data are valid 20 ns after the rising edge of the first clock period. srwe goes active 20 ns after the falling edge of the first clock period. srwe goes inactive 20 ns after the falling edge of the third clock period. address and data remain valid until the end of the third clock period. rise and fall times are nominally 5 ns. non-negative setup and hold times for address and data with respect to srwe are guaranteed. srwe has a pulse width of typically 100 ns, minimum 75 ns. static ram cycles ? programmed i/o architecture in the programmed i/o architecture mode, the sram is an 8-bit device connected to the pcnet-isa ii con- troller private bus, and can occupy up to 64 kbytes of address space. the sram is accessed through the isacsr0 and isacsr1 registers which serve as the sram data port and sram address pointer, respec- tively. since the isacsrs are used to access the sram, simple i/o accesses (to rap and idp) which are decoded by the pcnet-isa ii are used to access the sram without any external decoding logic. the rap and idp ports are naturally 16-bit resources and can be accessed with 16-bit isa i/o cycles if the io_mode bit (pnp 0xf0) is set. as discussed in the ethernet controller register cycles section, 8-bit i/o cycles are also allowed, provided the proper protocol is followed. this protocol requires that byte accesses must be performed in pairs, with the even byte access always being followed by associated odd byte access. in the programmed i/o architecture mode, when accessing the sram data port in particular (isacsr0), the restrictions on byte accesses are slightly different. even byte accesses (accesses where a0 = 0, sbhe = 1) may be performed to isacsr0 with- out any restriction. a corresponding odd byte access need not be performed following the even byte access as is required when accessing all other controller reg- isters. in fact, odd byte accesses (accesses where a0 = 1, sbhe = 1) may not be performed to isacsr0, ex- cept when they are the result of a software 16-bit access that are automatically converted to two byte ac- cesses by motherboard logic. since the internal pcnet-isa ii registers are used to access the sram in the programmed i/o architecture mode, the access cycle on the isa bus is identical to that described in the ethernet controller register cycles section. to minimize the number of i/o cycles required to access the sram, the pcnet-isa ii auto-increments the sram address pointer (isacsr1) by one or two following every read or write to the sram data port (isacsr0). if a single byte read or write to the sram data port occurs, the sram address pointer is auto- matically incremented by 1. if a word read or write to the sram data port occurs, the sram address pointer is automatically incremented by 2. this allows xtal1 (20 mhz) address sroe 19364b-18 static ram read cycle address/ data srwe xtal1 (20 mhz) static 19364b-19
90 am79c961a reads and writes to adjacent ascending addresses in the sram to be performed without intervening writes to the sram address pointer. since buffer accesses comprise a high percentage of all accesses to the sram, and buffer accesses are typically performed in adjacent ascending order, the auto-increment of the sram address pointer reduces the required isa bus cycles significantly. in addition to the auto-incrementing of the sram address pointer, the pcnet-isa ii performs write post- ing on writes to the sram and read prefetching on reads from the sram to maximize performance in the programmed i/o architecture mode. write posting: when a write cycle to the sram data port occurs, the pcnet-isa ii controller stores the data into an internal holding register, allowing the isa bus cycle to finish normally. the data in the holding register will then be written to the sram without the need for isa bus control. in the event that the holding register is already filled with unwritten sram data, the pcnet-isa ii controller will extend the isa write cycle by driving ochrdy low until the unwritten data is stored in the sram. once the data is written into the sram, the new write data is stored into the internal holding regis- ter and iochrdy is released allowing the isa bus cycle to complete. read prefetching: to gain performance on read accesses to the sram, the pcnet-isa ii performs prefetches of the sram after every read from the sram data port. the prefetch is performed using the speculated address that results from the auto-incre- ment that occurs on the sram address pointer follow- ing every access to the sram data port. following every read access, the 16-bit word following the just-read sram byte or word is prefetched and placed in a holding register. if a word read from the sram data port occurs before a ? prefetch invalidation event ? occurs, the prefetched word is driven onto the sd[15:0] pins without a wait state (no iochrdy low asser- tion). a ? prefetch invalidation event ? is defined as any activity on the private bus other than sram reads. this includes sram writes by either the isa bus or the network interface, address or boot prom reads, or any write to the sram address pointer. the pcnet-isa ii interface to the sram in the pro- grammed i/o architecture mode is identical to that in the shared memory architecture mode. hence, the sram read and write cycle descriptions and dia- grams shown in the ? static ram cycles ? shared memory architecture ? section apply. transmit operation the transmit operation and features of the pcnet-isa ii controller are controlled by programmable options. transmit function programming automatic transmit features, such as retry on collision, fcs generation/transmission, and pad field insertion, can all be programmed to provide flexibility in the (re-)transmission of messages. disable retry on collision (drty) is controlled by the drty bit of the mode register (csr15) in the initializa- tion block. automatic pad field insertion is controlled by the apad_xmt bit in csr4. if apad_xmt is set, auto- matic pad field insertion is enabled, the dxmtfcs fea- ture is over-ridden, and the 4-byte fcs will be added to the transmitted frame unconditionally. if apad_xmt is cleared, no pad field insertion will take place and runt packet transmission is possible. the disable fcs generation/transmission feature can be programmed dynamically on a frame by frame basis. see the add_fcs description of tmd1. transmit fifo watermark (xmtfw in csr80) sets the point at which the bmu (buffer management unit) requests more data from the transmit buffers for the fifo. this point is based upon how many 16-bit bus transfers (2 bytes) could be performed to the existing empty space in the transmit fifo. transmit start point (xmtsp in csr80) sets the point when the transmitter actually tries to go out on the media. this point is based upon the number of bytes written to the transmit fifo for the current frame. when the entire frame is in the fifo, attempts at trans- mission of preamble will commence regardless of the value in xmtsp. the default value of xmtsp is 10b, meaning 64 bytes full. automatic pad generation transmit frames can be automatically padded to ex- tend them to 64 data bytes (excluding preamble). this allows the minimum frame size of 64 bytes (512 bits) for 802.3/ethernet to be guaranteed with no software intervention from the host/controlling process. setting the apad_xmt bit in csr4 enables the automatic padding feature. the pad is placed between the llc data field and fcs field in the 802.3 frame. fcs is al- ways added if the frame is padded, regardless of the state of dxmtfcs. the transmit frame will be padded by bytes with the value of 00h. the default value of apad_xmt is 0, and this will disable auto pad genera- tion after reset. it is the responsibility of upper layer software to cor- rectly define the actual length field contained in the message to correspond to the total number of llc data bytes encapsulated in the packet (length field as defined in the ieee 802.3 standard). the length value contained in the message is not used by the pcnet-isa ii controller to compute the actual number of pad bytes
am79c961a 91 to be inserted. the pcnet-isa ii controller will append pad bytes dependent on the actual number of bits transmitted onto the network. once the last data byte of the frame has completed prior to appending the fcs, the pcnet-isa ii controller will check to ensure that 544 bits have been transmitted. if not, pad bytes are added to extend the frame size to this value, and the fcs is then added. the 544 bit count is derived from the following: minimum frame size (excluding preamble, including fcs) 64 bytes 512 bits preamble/sfd size 8 bytes 64 bits fcs size 4 bytes 32 bits to be classed as a minimum-size frame at the receiver, the transmitted frame must contain: preamble + (min frame size + fcs) bits at the point that fcs is to be appended, the transmitted frame should contain: preamble + (min frame size - fcs) bits 64+ (512- 32) bits a minimum-length transmit frame from the pcnet-isa ii controller will, therefore, be 576 bits after the fcs is appended. transmit fcs generation automatic generation and transmission of fcs for a transmit frame depends on the value of dxmtfcs bit in csr15. when dxmtfcs = 0 the transmitter will generate and append the fcs to the transmitted frame. if the automatic padding feature is invoked (apad_xmt is set in csr4), the fcs will be appended by the pcnet-isa ii controller regardless of the state of dxmtfcs. note that the calculated fcs is transmitted most-significant bit first. the default value of dxmtfcs is 0 after reset. transmit exception conditions exception conditions for frame transmission fall into two distinct categories; those which are the result of normal network operation, and those which occur due to abnormal network and/or host related events. normal events which may occur and which are handled autonomously by the pcnet-isa ii controller are basi- cally collisions within the slot time with automatic retry. the pcnet-isa ii controller will ensure that collisions which occur within 512 bit times from the start of trans- mission (including preamble) will be automatically retried with no host intervention. the transmit fifo en- sures this by guaranteeing that data contained within the fifo will not be overwritten until at least 64 bytes (512 bits) of data have been successfully transmitted onto the network. if 16 total attempts (initial attempt plus 15 retries) fail, the pcnet-isa ii controller sets the rtry bit in the cur- rent transmit tdte in host memory (tmd2), gives up ownership (sets the own bit to zero) for this packet, and processes the next packet in the transmit ring for transmission. iso 8802-3 (ieee/ansi 802.3) data frame preamble 1010....1010 sync 10101011 dest. addr srce. addr. length llc data pad fcs 56 bits 8 bits 6 bytes 6 bytes 2 bytes 46-1500 bytes 4 bytes 19364b-20
92 am79c961a abnormal network conditions include: loss of carrier late collision sqe test error (does not apply to 10base-t port.) these should not occur on a correctly configured 802.3 network, and will be reported if they do. when an error occurs in the middle of a multi-buffer frame transmission, the error status will be written in the current descriptor. the own bit(s) in the subse- quent descriptor(s) will be reset until the stp (the next frame) is found. loss of carrier a loss of carrier condition will be reported if the pc- net-isa ii controller cannot observe receive activity while it is transmitting on the aui port. after the pc- net-isa ii controller initiates a transmission, it will ex- pect to see data ? looped back ? on the di pair. this will internally generate a ? carrier sense, ? indicating that the integrity of the data path to and from the mau is intact, and that the mau is operating correctly. this ? carrier sense ? signal must be asserted before the end of the transmission. if ? carrier sense ? does not become active in response to the data transmission, or becomes inac- tive before the end of transmission, the loss of carrier (lcar) error bit will be set in tmd2 after the frame has been transmitted. the frame will not be re-tried on the basis of an lcar error. in 10base-t mode lcar will indicate that jabber or link fail state has occurred. late collision a late collision will be reported if a collision condition occurs after one slot time (512 bit times) after the trans- mit process was initiated (first bit of preamble com- menced). the pcnet-isa ii controller will abandon the transmit process for the particular frame, set late col- lision (lcol) in the associated tmd3, and process the next transmit frame in the ring. frames experiencing a late collision will not be re-tried. recovery from this condition must be performed by upper-layer software. sqe test error during the inter packet gap time following the comple- tion of a transmitted message, the aui ci pair is asserted by some transceivers as a self-test. the inte- gral manchester encoder/decoder will expect the sqe test message (nominal 10 mhz sequence) to be returned via the ci pair within a 40 network bit time period after di pair goes inactive. if the ci inputs are not asserted within the 40 network bit time period fol- lowing the completion of transmission, then the pc- net-isa ii controller will set the cerr bit in csr0. cerr will be asserted in 10base-t mode after trans- mit if t-mau is in link fail state. cerr will never cause intr to be activated. it will, however, set the err bit in csr0. host related transmit exception conditions include buff and uflo as described in the transmit descrip- tor section. receive operation the receive operation and features of the pcnet-isa ii controller are controlled by programmable options. receive function programming automatic pad field stripping is enabled by setting the astrp_rcv bit in csr4; this can provide flexibility in the reception of messages using the 802.3 frame format. all receive frames can be accepted by setting the prom bit in csr15. when prom is set, the pc- net-isa ii controller will attempt to receive all mes- sages, subject to minimum frame enforcement. promiscuous mode overrides the effect of the disable receive broadcast bit on receiving broadcast frames. the point at which the bmu will start to transfer data from the receive fifo to buffer memory is controlled by the rcvfw bits in csr80. the default established during reset is 10b, which sets the threshold flag at 64 bytes empty. automatic pad stripping during reception of an 802.3 frame the pad field can be stripped automatically. astrp_rcv (bit 10 in csr4) = 1 enables the automatic pad stripping feature. the pad field will be stripped before the frame is passed to the fifo, thus preserving fifo space for additional frames. the fcs field will also be stripped, since it is computed at the transmitting station based on the data and pad field characters, and will be invalid for a receive frame that has had the pad characters stripped. the number of bytes to be stripped is calculated from the embedded length field (as defined in the ieee 802.3 definition) contained in the frame. the length indicates the actual number of llc data bytes con- tained in the message. any received frame which con- tains a length field less than 46 bytes will have the pad field stripped (if astrp_rcv is set). receive frames which have a length field of 46 bytes or greater will be passed to the host unmodified. since any valid ethernet type field value will always be greater than a normal 802.3 length field ( 46), the pc- net-isa ii controller will not attempt to strip valid ether- net frames. note that for some network protocols the value passed in the ethernet type and/or 802.3 length field is not compliant with either standard and may cause problems. the diagram below shows the byte/bit ordering of the received length field for an 802.3 compatible frame format.
am79c961a 93 ieee/ansi 802.3 frame and length field transmission order receive fcs checking reception and checking of the received fcs is per- formed automatically by the pcnet-isa ii controller. note that if the automatic pad stripping feature is enabled, the received fcs will be verified against the value computed for the incoming bit stream including pad characters, but it will not be passed to the host. if a fcs error is detected, this will be reported by the crc bit in rmd1. receive exception conditions exception conditions for frame reception fall into two distinct categories; those which are the result of normal network operation, and those which occur due to abnormal network and/or host related events. normal events which may occur and which are handled autonomously by the pcnet-isa ii controller are basi- cally collisions within the slot time and automatic runt packet rejection. the pcnet-isa ii controller will ensure that collisions which occur within 512 bit times from the start of reception (excluding preamble) will be automat- ically deleted from the receive fifo with no host inter- vention. the receive fifo will delete any frame which is composed of fewer than 64 bytes provided that the runt packet accept (rpa bit in csr124) feature has not been enabled. this criteria will be met regardless of whether the receive frame was the first (or only) frame in the fifo or if the receive frame was queued behind a previously received message. abnormal network conditions include: fcs errors late collision these should not occur on a correctly configured 802.3 network and will be reported if they do. host related receive exception conditions include miss, buff, and oflo. these are described in the receive descriptor section. loopback operation loopback is a mode of operation intended for system diagnostics. in this mode, the transmitter and receiver are both operating at the same time so that the controller receives its own transmissions. the control- ler provides two types of internal loopback and three types of external loopback. in internal loopback mode, the transmitted data can be looped back to the receiver at one of two places inside the controller without actu- ally transmitting any data to the external network. the receiver will move the received data to the next receive buffer, where it can be examined by software. alterna- tively, external loopback causes transmissions to go off-chip. for the aui port, frame transmission occurs normally and assumes that an external mau will loop the frame back to the chip. for the 10base-t port, two external loopback options are available, both of which require a valid link pass state and both of which trans- mit data frames at the rj45 interface. selection of these modes is defined by the tmau_loope bit in isacsr2. one option loops the data frame back inside the chip, and is compatible with a ? live ? network. the preamble 1010....1010 synch 10101011 dest. addr. srce. addr. length llc data pad fcs 56 bits 8 bits 6 bytes 6 bytes 2 bytes bytes 4 bytes most significant byte least significant byte bit 0 bit 7 start of packet at time= 0 increasing time bit 7 bit 0 45 ? 0 bytes 1 ? 1500 bytes 19364b-21
94 am79c961a other option requires an external device (such as a ? loopback plug ? ) to loop the data back to the chip, a function normally not available on a 10base-t network. the pcnet-isa ii chip has two dedicated fcs genera- tors, eliminating the traditional lance limitations on loopback fcs operation. the receive fcs generation logic is always enabled. the transmit fcs generation logic can be disabled (to emulate lance type loop- back operation) by setting the dxmtfcs bit in the mode register (csr15). in this configuration, software must generate the fcs and append the four fcs bytes to the transmit frame data. the loopback facilities of the mac engine allow full operation to be verified without disturbance to the net- work. loopback operation is also affected by the state of the loopback control bits (loop, mendecl, and intl) in csr15. this affects whether the internal mendec is considered part of the internal or external loop- backpath. the receive fcs generation logic in the pcnet-isa ii chip is used for multicast address detection. since this fcs logic is always enabled, there are no restrictions to the use of multicast addressing while in loopback mode. when performing an internal loopback, no frame will be transmitted to the network. however, when the pc- net-isa ii controller is configured for internal loopback the receiver will not be able to detect network traffic. external loopback tests will transmit frames onto the network if the aui port is selected, and the pcnet-isa ii controller will receive network traffic while configured for external loopback when the aui port is selected. runt packet accept is automatically enabled when any loopback mode is invoked. loopback mode can be performed with any frame size. runt packet accept is internally enabled (rpa bit in csr124 is not affected) when any loopback mode is invoked. this is to be backwards compatible to the lance (am7990) software. leds the pcnet-isa ii controller ? s led control logic allows programming of the status signals, which are displayed on 3 led outputs. one led (led0 ) is dedicated to dis- playing 10base-t link status. the status signals available are collision, jabber, receive, receive polar- ity, transmit, receive address match, and full duplex link status. if more than one status signal is enabled, they are ored together. an optional pulse stretcher is available for each programmable output. this allows emulation of the tpex (am79c98) and tpex + (am79c100) led outputs. each status signal is anded with its corresponding enable signal. the enabled status signals run to a com- mon or gate: the output from the or gate is run through a pulse stretcher, which consists of a 3-bit shift register clocked at 38 hz. the data input of the shift register is at logic 0. the or gate output asynchronously sets all three bits of the shift register when its output goes active. the output of the shift register controls the associated ledx pin. thus, the pulse stretcher provides an led output of 52 ms to 78 ms. signal behavior col active during collision activity on the network fdls active when full duplex operation is enabled and functioning on the selected network port jab active when the pcnet-isa ii is jabbering on the network lnkst active during link ok not active during link down rcv active while receiving data rvpol active during receive polarity is ok not active during reverse receive polarity rcvaddm active during receive with address match xmt active while transmitting data and fdls fdlse and rcvm rcvm e and xmt xmt e and rvpol rvpol e and rcv rcv e and jab jab e and col col e or to pulse stretcher and rcvaddm rcvadde 19364b-22 led control logic
am79c961a 95 refer to the section ? isa bus configuration registers ? for information on led control via the isacsrs. magic packet operation in the magic packet mode, pcnet-isa ii completes any transmit and receive operations in progress, suspends normal activity, and enters into a state where only a magic packet could be detected. a magic packet frame is a frame that contains a data sequence which repeats the physical address (padr[47:00]) at least sixteen times frame sequentially, with bit[00] received first. in magic packet suspend mode, the pcnet-isa ii remains powered up. slave accesses to the pcnet-isa ii are still possible, the same as any other mode. all of the received packets are flushed from the receive fifo. an led and/or interrupt pin could be activated, indicating the receive of a magic packet frame. this indication could be used for a variety of management tasks. magic packet mode activation this mode can be enabled by either software or exter- nal hardware means, but in either case, the mp_mode bit (csr5, bit 1) must be set first. hardware activation. this is done by driving the sleep pin low. deasserting the sleep pin will return the pcnet-isa ii to normal operation. software activation. this is done by setting the mp_enbl bit (csr5, bit 2). resetting this bit will return the pcnet-isa ii to normal operation. magic packet receive indicators the reception of a magic packet can be indicated either through one of the leds 1, 2 or 3, and/or the activation of the interrupt pin. mp_int bit (csr5, bit 4) will also be set upon the receive of the magic packet. led indication . either one of the leds 1, 2, or 3 could be activated by the receive of the magic packet. the ? magic packet enable ? bit (bit 9) in the isacsr 5, 6 or 7 should be set to enable this feature. note that the polarity of the led2 could be controlled by the ledxor bit (isacsr6, bit 14). the led could be deactivated by setting the stop bit or resetting the mp_enbl bit (csr5, bit 2). interrupt indication . interrupt pin could be activated by the receive of the magic packet. the mp_i_enbl bit (csr5, bit 3) and iena bit (csr0, bit 6) should be set to enable this feature. bit name description 1 mp_mode magic packet mode. setting this bit is a prerequisite for entering the magic packet mode. it also redefines the sleep pin to be a magic packet enable pin. read/write accessi- ble always. it is cleared by as- serting the reset pin, or read- ing the reset register. 2 mp_enbl magic packet enable. this bit when set, will force the pcnet-isa ii into the magic packet mode. read/write ac- cessible always. it is cleared by asserting the reset pin or reading the reset register. 3 mp_i_enbl magic packet interrupt enable. acts as an unmask bit for the mp_int (csr5, bit 4). read/ write accessible always. it is cleared by asserting the reset pin or reading the reset regis- ter, or setting the stop bit. 4 mp_int magic packet receive interrupt. will be set when a magic packet has been received. writing a ? one ? will clear this bit. it is cleared by asserting the reset pin, or reading the reset regis- ter. 9 mp magic packet led enable. when set, the led output will be asserted to indicate that a magic packet has been received.
96 am79c961a pcnet-isa ii controller registers the pcnet-isa ii controller implements all lance (am7990) registers, plus a number of additional regis- ters. the pcnet-isa ii controller registers are compat- ible with the original lance, but there are some places where previously reserved lance bits are now used by the pcnet-isa ii controller. if the reserved lance bits were used as recommended, there should be no compatibility problems. register access internal registers are accessed in a two-step operation. first, the address of the register to be accessed is writ- ten into the register address port (rap). subsequent read or write operations will access the register pointed to by the contents of the rap. the data will be read from (or written to) the selected register through the data port, either the register data port (rdp) for control and status registers (csr) or the isacsr register data port (idp) for isa control and status registers (isacsr). rap: register address port bit name description 15-7 res reserved locations. read and written as zeroes. 6-0 rap register address port select. selects the csr or isacsr location to be accessed. rap is cleared by reset. control and status registers csr0: pcnet-isa ii controller status register bit name description 15 err error is set by the oring of babl, cerr, miss, and merr. err remains set as long as any of the error flags are true. err is read only; write opera- tions are ignored. 14 babl babble is a transmitter time-out error. it indicates that the trans- mitter has been on the channel longer than the time required to send the maximum length frame. babl will be set if 1519 bytes or greater are transmitted. when babl is set, irq is as- serted if iena = 1 and the mask bit bablm (csr3.14) is clear. babl assertion will set the err bit. babl is set by the mac layer and cleared by writing a ? 1". writing a ? 0" has no effect. babl is cleared by reset or by set- ting the stop bit. 13 cerr collision error indicates that the collision inputs to the aui port failed to activate within 20 net- work bit times after the chip ter- minated transmission (sqe test). this feature is a transceiv- er test feature. cerr will be set in 10base-t mode during transmit if in link fail state. cerr assertion will not result in an interrupt being generated. cerr assertion will set the err bit. cerr is set by the mac layer and cleared by writing a ? 1". writing a ? 0" has no effect. cerr is cleared by reset or by setting the stop bit. 12 miss missed frame is set when pc- net-isa ii controller has lost an incoming receive frame because a receive descriptor was not available. this bit is the only in- dication that receive data has been lost since there is no re- ceive descriptor available for status information. when miss is set, irq is asserted if iena = 1 and the mask bit missm (csr3.12) is clear. miss assertion will set the err bit. miss is set by the buffer man- agement unit and cleared by writ- ing a ? 1". writing a ? 0" has no effect. miss is cleared by reset or by setting the stop bit. 11 merr memory error is set when pc- net-isa ii controller is a bus master and has not received dack assertion after 50 s after drq assertion. memory error indicates that pcnet-isa ii con- troller is not receiving bus mas- tership in time to prevent over- flow/underflow conditions in the receive and transmit fifos. (merr indicates a slightly differ- ent condition for the lance; for the lance merr occurs when ready has not been asserted 25.6 s after the address has been asserted.) when merr is set, irq is as- serted if iena = 1 and the mask bit merrm (csr3.11) is clear. merr assertion will set the err bit.
am79c961a 97 merr is set by the bus inter- face unit and cleared by writing a ? 1". writing a ? 0" has no effect. merr is cleared by reset or by setting the stop bit. 10 rint receive interrupt is set after re- ception of a receive frame and toggling of the own bit in the last buffer in the receive descriptor ring. when rint is set, irq is assert- ed if iena = 1 and the mask bit rintm (csr3.10) is clear. rint is set by the buffer man- agement unit after the last receive buffer has been updated and cleared by writing a ? 1". writing a ? 0" has no effect. rint is cleared by reset or by setting the stop bit. 9 tint transmit interrupt is set after transmission of a transmit frame and toggling of the own bit in the last buffer in the transmit descriptor ring. when tint is set, irq is asserted if iena = 1 and the mask bit tintm (csr3.9) is clear. tint is set by the buffer man- agement unit after the last trans- mit buffer has been updated and cleared by writing a ? 1". writing a ? 0" has no effect. tint is cleared by reset or by setting the stop bit. 8 idon initialization done indicates that the initialization sequence has completed. when idon is set, pcnet-isa ii controller has read the initialization block from memory. when idon is set, irq is assert- ed if iena = 1 and the mask bit idonm (csr3.8) is clear. idon is set by the buffer man- agement unit after the initializa- tion block has been read from memory and cleared by writing a ? 1". writing a ? 0" has no effect. idon is cleared by reset or by setting the stop bit. 7 intr interrupt flag indicates that one or more of the following interrupt causing conditions has occurred: babl, miss, merr, mpco, rcvcco, rint, tint, idon, jab or txstrt; and its associated mask bit is clear. if iena = 1 and intr is set, irq will be active. intr is cleared automatically when the condition that caused interrupt is cleared. intr is read only. intr is cleared by reset or by setting the stop bit. 6 iena interrupt enable allows irq to be active if the interrupt flag is set. if iena = ? 0" then irq will be disabled regardless of the state of intr. iena is set by writing a ? 1" and cleared by writing a ? 0". iena is cleared by reset or by setting the stop bit. 5 rxon receive on indicates that the receive function is enabled. rxon is set if drx (csr15.0) = ? 0" after the start bit is set. if init and start are set togeth- er, rxon will not be set until after the initialization block has been read in. rxon is read only. rxon is cleared by reset or by setting the stop bit. 4 txon transmit on indicates that the transmit function is enabled. txon is set if dtx (csr15.1) = ? 0" after the start bit is set. if init and start are set togeth- er, txon will not be set until after the initialization block has been read in. txon is read only. txon is cleared by reset or by setting the stop bit. 3 tdmd transmit demand, when set, causes the buffer management unit to access the transmit descriptor ring without waiting for the poll-time counter to elapse. if txon is not enabled, tdmd bit will be reset and no transmit descriptor ring access will occur. tdmd is required to be set if the dpoll bit in csr4 is set; setting tdmd while dpoll = 0 merely hastens the pcnet-isa ii controller ? s re- sponse to a transmit descriptor ring entry. tdmd is set by writing a ? 1". writing a ? 0" has no effect. tdmd will be cleared by the buffer management unit when it fetches a transmit descriptor.
98 am79c961a tdmd is cleared by reset or by setting the stop bit. 2 stop stop assertion disables the chip from all external activity. the chip remains inactive until either strt or init are set. if stop, strt and init are all set together, stop will override strt and init. stop is set by writing a ? 1" or by reset. writing a ? 0" has no ef- fect. stop is cleared by setting either strt or init. 1 strt strt assertion enables pcnet- isa ii controller to send and receive frames, and perform buffer management operations. setting strt clears the stop bit. if strt and init are set to- gether, pcnet-isa ii controller initialization will be performed first. strt is set by writing a ? 1". writ- ing a ? 0" has no effect. strt is cleared by reset or by setting the stop bit. 0 init init assertion enables pc- net-isa ii controller to begin the initialization procedure which reads in the initialization block from memory. setting init clears the stop bit. if strt and init are set together, pcnet-isa ii controller initialization will be performed first. init is not cleared when the initialization sequence has completed. init is set by writing a ? 1". writ- ing a ? 0" has no effect. init is cleared by reset or by setting the stop bit. csr1: iadr[15:0] bit name description 15-0 iadr [15:0] lower address of the initializa- tion address register. bit location 0 must be zero. whenever this register is written, csr16 is updated with csr1 ? s contents. read/write accessible only when the stop or spnd bits are set. unaffected by reset. csr2: iadr[23:16] bit name description 15-8 res reserved locations. read and written as zero. 7-0 iadr [23:16] upper 8 bits of the address of the initialization block. bit loca- tions 15-8 must be written with zeros. whenever this register is written, csr17 is updated with csr2 ? s contents. read/write accessible only when the stop or spnd bits are set. unaffected by reset. csr3: interrupt masks and deferral control bit name description 15 res reserved location. written as zero and read as undefined. 14 bablm babble mask. if bablm is set, the babl bit in csr0 will be masked and will not set intr flag in csr0. bablm is cleared by reset and is not affected by stop. 13 res reserved location. written as zero and read as undefined. 12 missm missed frame mask. if missm is set, the miss bit in csr0 will be masked and will not set intr flag in csr0. missm is cleared by reset and is not affected by stop. 11 merrm memory error mask. if merrm is set, the merr bit in csr0 will be masked and will not set intr flag in csr0. merrm is cleared by reset and is not affected by stop. 10 rintm receive interrupt mask. if rintm is set, the rint bit in csr0 will be masked and will not set intr flag in csr0. rintm is cleared by reset and is not affected by stop. 9 tintm transmit interrupt mask. if tintm is set, the tint bit in csr0 will be masked and will not set intr flag in csr0. tintm is cleared by reset and is not affected by stop. 8 idonm initialization done mask. if idonm is set, the idon bit in csr0 will be masked and will not set intr flag in csr0. idonm is cleared by reset and is not affected by stop. 7 res reserved locations. written as zero and read as undefined. 6 dxsuflo disable transmit stop on underflow error.
am79c961a 99 when dxsuflo is set to zero, the transmitter is turned off when an uflo error occurs (csr0, txon = 0). when dxsuflo is set to one, the pcnet-isa ii controller gracefully recovers from an uflo error. it scans the transmit descriptor ring until it finds the start of a new frame and starts a new transmission. read/write accessible always. dxsuflo is cleared by asserting the reset pin or reading the reset register and is not affected by stop. 5 lappen look ahead packet processing (lappen). when set to a one, the lappen bit will cause the pcnet-isa ii controller to gener- ate an interrupt following the descriptor write operation to the first buffer of a receive packet. this interrupt will be generated in addition to the interrupt that is generated following the descrip- tor write operation to the last buffer of a receive packet. the interrupt will be signaled through the rint bit of csr0. setting lappen to a one also enables the pcnet-isa ii con- troller to read the stp bit of the receive descriptors. pcnet-isa ii controller will use stp infor- mation to determine where it should begin writing a receive packet ? s data. note that while in this mode, the pcnet-isa ii con- troller can write intermediate packet data to buffers whose descriptors do not contain stp bits set to one. following the write to the last descriptor used by a packet, the pcnet-isa ii controller will scan through the next descriptor entries to locate the next stp bit that is set to a one. the pcnet-isa ii controller will begin writing the next pack- et ? s data to the buffer pointed to by that descriptor. note that because several descriptors may be allocated by the host for each packet, and not all messages may need all of the descriptors that are allocated between descriptors that contain stp = one, then some descrip- tors/buffers may be skipped in the ring. while performing the search for the next stp bit that is set to one, the pcnet-isa ii controller will advance through the receive descriptor ring regardless of the state of owner- ship bits. if any of the entries that are examined during this search indicate own = one, pcnet-isa ii will reset the own bit to zero in these entries. if a scanned entry indicates host ownership with stp= ? 0", then the pcnet-isa ii controller will not alter the entry, but will advance to the next entry. when the stp bit is found to be true, but the descriptor that con- tains this setting is not owned by the pcnet-isa ii controller, then the pcnet-isa ii controller will stop advancing through the ring entries and begin periodic poll- ing of this entry. when the stp bit is found to be true, and the descriptor that contains this set- ting is owned by the pcnet-isa ii controller, then the pcnet-isa ii controller will stop advancing through the ring entries, store the descriptor information that is has just read, and wait for the next receive to arrive. this behavior allows the host software to pre-assign buffer space in such a manner that the ? header ? portion of a receive packet will always be written to a particular memory area, and the ? data ? portion of a receive pack- et will always be written to a sep- arate memory area. the inter- rupt is generated when the ? header ? bytes have been writ- ten to the ? header ? memory area. read/write accessible always. the lappen bit will be reset zero by reset and will unaffected by the stop. see appendix e for more information on lapp. 4 dxmt2pd disable transmit two part deferral. (described in the media access management section). if dxmt2pd is set, transmit two part deferral will be disabled. dxmt2pd is cleared by reset and is not affected by stop. 3 emba enable modified back-off algo- rithm. if emba is set, a modified
100 am79c961a back-off algorithm is implemented as described in the media access management section. read/write accessible. emba is cleared by reset and is not affected by stop. 2-0 res reserved locations. written as zero and read as undefined. csr4: test and features control bit name description 15 entst enable test mode operation. when entst is set, writing to test mode registers csr124 and csr126 is allowed, and other register test functions are enabled. in order to set entst, it must be written with a ? 1" during the first write access to csr4 after reset. once a ? 0" is writ- ten to this bit location, entst cannot be set until after the pc- net-isa ii controller is reset. entst is cleared by reset. 14 dmaplus when dmaplus = ? 1", the burst transaction counter in csr80 is disabled. if dmaplus = ? 0", the burst transaction counter is enabled. caution : when using dmaplus and/or timer bits in a pc environment, care must be taken not to hold the bus for more than the required refresh time. dmaplus is cleared by reset. 13 timer timer enable register. if timer is set, the bus activity timer reg- ister (csr82) is enabled and the pcnet-isa ii may perform any combination of accesses (buffer reads, buffer writes, descriptor reads, and descriptor writes) during a single bus mastership period. the bus is held until either the bus activity timer expires or there are no further pending operations to be per- formed. the pcnet-isa ii deter- mines whether there are further pending bus operations by wait- ing approximately 1 s after the completion of every bus opera- tion (e.g. a descriptor or fifo access). if, during the 1 s period, no further bus operations are requested by the internal buffer management unit, the pcnet-isa ii determines that there are no further pending operations and gives up bus ownership. if timer is cleared, the bus activity timer register is dis- abled and the pcnet-isa ii per- forms only one type of access (descriptor read, descriptor write, buffer read, or buffer write) and buffer accesses are performed to adjacent ascending addresses during each bus mastership period. timer is cleared by reset. 12 dpoll disable transmit polling. if dpoll is set, the buffer man- agement unit will disable trans- mit polling. likewise, if dpoll is cleared, automatic transmit poll- ing is enabled. if dpoll is set, tdmd bit in csr0 must be peri- odically set in order to initiate a manual poll of a transmit descriptor. transmit descriptor polling will not take place if txon is reset. dpoll is cleared by reset. 11 apad_xmt auto pad transmit. when set, apad_xmt enables the auto- matic padding feature. transmit frames will be padded to extend them to 64 bytes, including fcs. the fcs is calculated for the en- tire frame (including pad) and appended after the pad field. apad_xmt will override the programming of the dxmtfcs bit (csr15.3). apad_ xmt is reset by activa- tion of the reset pin. 10 astrp_rcv astrp_rcv enables the auto- matic pad stripping feature. the pad and fcs fields will be stripped from receive frames and not placed in the fifo. astrp_ rcv is reset by activa- tion of the reset pin. 9 mfco missed frame counter overflow interrupt. this bit indicates the mfc (csr112) has overflowed. can be cleared by writing a ? 1" to this bit. also cleared by reset or setting the stop bit. writing a ? 0" has no effect. 8 mfcom missed frame counter overflow mask. if mfcom is set, mfco will not set intr in csr0.
am79c961a 101 mfcom is set by reset and is not affected by stop. 7-6 res reserved locations. read and written as zero. 5 rcvcco receive collision counter over- flow. this bit indicates the receive collision counter (csr114) has overflowed. it can be cleared by writing a 1 to this bit. also cleared by reset or setting the stop bit. writing a 0 has no effect. 4 rcvccom receive collision counter over- flow mask. if rcvccom is set, rcvcco will not set intr in csr0. rcvccom is set by reset and is not affected by stop. 3 txstrt transmit start status is set when- ever pcnet-isa ii controller begins transmission of a frame. when txstrt is set, irq is asserted if iena = 1 and the mask bit txstrtm (csr4.2) is clear. txstrt is set by the mac unit and cleared by writing a ? 1", set- ting reset or setting the stop bit. writing a ? 0" has no effect. 2 txstrtm transmit start mask. if txstrtm is set, the txstrt bit in csr4 will be masked and will not set intr flag in csr0. txstrtm is set by reset and is not affected by stop. 1 jab jabber error is set when the pcnet-isa ii controller twist- ed-pair mau function exceeds an allowed transmission limit. jabber is set by the tmau cir- cuit and can only be asserted in 10base-t mode. when jab is set, irq is assert- ed if iena = 1 and the mask bit jabm (csr4.4) is clear. the jab bit can be reset even if the jabber condition is still present. jab is set by the tmau circuit and cleared by writing a ? 1". writing a ? 0" has no effect. jab is also cleared by reset or set- ting the stop bit. 0 jabm jabber error mask. if jabm is set, the jab bit in csr4 will be masked and will not set intr flag in csr0. jabm is set by reset and is not affected by stop. csr5: control 1 bit name description 0 spnd suspend. setting spnd to one will cause the pcnet-isa ii con- troller to start entering the sus- pend mode. the host must poll spnd until it reads a one back, to determine that the pcnet-isa ii controller has entered the sus- pend mode. setting spnd to zero will get the pcnet-isa ii controller out of suspend mode and back into its active state. spnd can only be set to one if stop (csr0, bit 2) is set to zero. asserting the reset pin, reading the reset register, or setting the stop bit forces the pcnet-isa ii controller out of suspend mode. when the host requests the pc- net-isa ii controller to enter the suspend mode, the device first finishes all on-going transmit activity and updates the corresponding transmit descrip- tor entries. it then completes any frame reception occurring at the time the spnd bit was set, and updates the corre- sponding receive descriptor en- tries. any subsequent frames incident upon the pcnet-isa ii during suspend mode will not be received, nor will any notifi- cation be given as to the missed frames (the miss bit in csr0 will not be updated while in sus- pend mode). it then sets the read-version of spnd to one and enters the suspend mode. in suspend mode, all of the csr registers are accessible. as long as the pcnet-isa ii controller is not reset while in suspend mode (by asserting the reset pin, reading the reset register, or setting the stop bit), no reinitialization of the device is required after the device comes out of suspend mode. the pcnet-isa ii control- ler will continue at the transmit and receive descriptor ring locations, where it had left, when it entered the suspend mode.
102 am79c961a read/write accessible always. spnd is cleared by asserting the reset pin, reading the reset register, or setting the stop bit 1 mp_mode magic packet mode. setting this bit is a prerequisite for entering the magic packet mode. it also redefines the sleep pin to be a magic packet enable pin. read/write accessi- ble always. it is cleared by as- serting the reset pin, or read- ing the reset register. 2 mp_enbl magic packet enable. this bit when set, will force the pcnet-isa ii into the magic packet mode. read/write ac- cessible always. it is cleared by asserting the reset pin or reading the reset register. 3 mp_i_enbl magic packet interrupt enable. acts as an unmask bit for the mp_int (csr5, bit 4). read/ write accessible always. it is cleared by asserting the reset pin or reading the reset regis- ter, or setting the stop bit. 4 mp_int magic packet receive interrupt. will be set when a magic packet has been received. writing a ? one ? will clear this bit. it is cleared by asserting the reset pin, or reading the reset regis- ter. csr6: rcv/xmt descriptor table length bit name description 15-12 tlen contains a copy of the transmit encoded ring length (tlen) field read from the initialization block during pcnet-isa ii controller ini- tialization. this field is written during the pcnet-isa ii controller initialization routine. read accessible only when stop or spnd bits are set. write oper- ations have no effect and should not be performed. tlen is only defined after initialization. 11-8 rlen contains a copy of the receive encoded ring length (rlen) read from the initialization block during pcnet-isa ii con- troller initialization. this field is written during the pcnet-isa ii controller initialization routine. read accessible only when stop or spnd bits are set. write operations have no effect and should not be performed. rlen is only defined after initialization. 7-0 res reserved locations. read as zero. write operations should not be performed. csr8: logical address filter, ladrf[15:0] bit name description 15-0 ladrf[15:0] logical address filter, ladrf [15:0]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. read/write accessible only when stop or spnd bits are set. csr9: logical address filter, ladrf[31:16] bit name description 15-0 ladrf[31:16] logical address filter, ladrf[31:16]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. read/write accessible only when stop or spnd bits are set. csr10: logical address filter, ladrf[47:32] bit name description 15-0 ladrf[47:32] logical address filter, ladrf[47:32]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. read/write accessible only when stop or spnd bits are set. csr11: logical address filter, ladrf[63:48] bit name description 15-0 ladrf[63:48] logical address filter, ladrf[63:48]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register.
am79c961a 103 read/write accessible only when stop or spnd bits are set. csr12: physical address register, padr[15:0] bit name description 15-0 padr[15:0] physical address register, padr[15:0]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. the padr bits are transmitted padr[0] first and padr[47] last. read/write accessible only when stop or spnd bits are set. csr13: physical address register, padr[31:16] bit name description 15-0padr[31:16] physical address register, padr[31:16]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. the padr bits are transmitted padr[0] first and padr[47] last. read/write accessible only when stop or spnd bits are set. csr14: physical address register, padr[47:32] bit name description 15-0 padr[47:32] physical address register, padr[47:32]. undefined until initialized either automatically by loading the initialization block or directly by an i/o write to this register. the padr bits are transmitted padr[0] first and padr[47] last. read/write accessible only when stop or spnd bits are set. csr15: mode register bit name description this register ? s fields are loaded during the pcnet-isa ii controller initialization routine with the cor- responding initialization block values. the register can also be loaded directly by an i/o write. activating the reset pin clears all bits of csr15 to zero. 15 prom promiscuous mode. when prom = ? 1", all incoming receive frames are accepted. read/write accessible only when stop or spnd bits are set. 14 drcvbc disablereceivebroadcast . when set, disables the pcnet-isa ii controller from receiving broad- cast messages. used for proto- cols that do not support broadcast addressing, except as a function of multicast. drcvbc is cleared by activation of the reset pin (broadcast messages will be received). read/write accessible only when stop or spnd bits are set. 13 drcvpa disable receive physical ad- dress. when set, the physical address detection (station or node id) of the pcnet-isa ii con- troller will be disabled. frames addressed to the nodes individual physical address will not be recognized (although the frame may be accepted by the eadi mechanism). read/write accessible only when stop or spnd bits are set. 12 dlnktst disable link status. when dlnktst = ? 1", monitoring of link pulses is disabled. when dlnktst = ? 0", monitoring of link pulses is enabled. this bit only has meaning when the 10base-t network interface is selected. read/write accessible only when stop or spnd bits are set. 11 dapc disable automatic polarity correction. when dapc = ? 1", the 10base-t receive polarity reversal algorithm is disabled. likewise, when dapc = ? 0", the polarity reversal algorithm is enabled. this bit only has meaning when the 10base-t network interface is selected. read/write accessible only when stop or spnd bits are set.
104 am79c961a 10 mendecl mendec loopback mode. see the description of the loop bit in csr15. read/write accessible only when stop or spnd bits are set. 9 lrt/tsel low receive threshold (t-mau mode only) transmit mode select (aui mode only) lrt low receive threshold. when lrt = ? 1", the internal twisted pair receive thresholds are reduced by 4.5 db below the standard 10base-t value (approximately 3/5) and the unsquelch threshold for the rxd circuit will be 180-312 mv peak. when lrt = ? 0", the unsquelch threshold for the rxd circuit will be the standard 10base-t value, 300-520 mv peak. in either case, the rxd circuit post squelch threshold will be one half of the unsquelch thresh- old. this bit only has meaning when the 10base-t network interface is selected. read/write accessible only when stop or spnd bits are set. cleared by reset. tsel transmit mode select. tsel controls the levels at which the aui drivers rest when the aui transmit port is idle. when tsel = 0, do+ and do- yield ? zero ? dif- ferential to operate transformer coupled loads (ethernet 2 and 802.3). when tsel = 1, the do+ idles at a higher value with respect to do-, yielding a logical high state (ethernet 1). this bit only has meaning when the aui network interface is selected. not available under auto-select mode. read/write accessible only when stop or spnd bits are set. cleared by reset. 8-7 portsel port select bits allow for software [1:0] controlled selection of the net- work medium. portsel active only when media-select bit set to 0 in isacsr2. read/write accessible only when stop or spnd bits are set. cleared by reset. the network port configuration are as follows: 6 intl internal loopback. see the description of loop, csr15.2. read/write accessible only when stop bit is set. 5 drty disable retry. when drty = ? 1", pcnet-isa ii controller will attempt only one transmission. if drty = ? 0", pcnet-isa ii con- troller will attempt to transmit 16 times before signaling a retry error. read/write accessible only when stop or spnd bits are set. 4 fcoll force collision. this bit allows the collision logic to be tested. pcnet-isa ii controller must be in internal loopback for fcoll to be valid. if fcoll = ? 1", a col- lision will be forced during loop- back transmission attempts; a retry error will ultimately result. if fcoll = ? 0", the force colli- sion logic will be disabled. read/write accessible only when stop or spnd bits are set. 3 dxmtfcs disable transmit crc (fcs). when dxmtfcs = ? 0", the transmitter will generate and append a fcs to the transmitted frame. when dxmtfcs = ? 1", the fcs logic is allocated to the receiver and no fcs is generat- ed or sent with the transmitted frame. see also the add_fcs bit in tmd1. if dxmtfcs is set, no fcs will be generated. if both dxmtfcs is set and add_fcs is clear for a particular frame, no fcs will be generated. if add_fcs is set for a particular frame, the state of dxmtfcs is ignored and a fcs will be ap- pended on that frame by the transmit circuitry. portsel[1:0] network port 0 0 aui 0 1 10base-t 1 0 gpsi* 1 1 reserved *refer to the section on general purpose serial interface for detailed information on accessing gpsi.
am79c961a 105 in loopback mode, this bit deter- mines if the transmitter appends fcs or if the receiver checks the fcs. this bit was called dtcr in the lance (am7990). read/write accessible only when stop or spnd bits are set. 2 loop loopback enable allows pc- net-isa ii controller to operate in full duplex mode for test purpos- es. when loop = ? 1", loopback is enabled. in combination with intl and mendecl, various loopback modes are defined as follows. read/write accessible only when stop or spnd bits are set. loop is cleared by reset. 1 dtx disable transmit. if this bit is set, the pcnet-isa ii controller will not access the transmit descriptor ring and, therefore, no transmissions will occur. dtx = ? 0" will set txon bit (csr0.4) after strt (csr0.1) is assert- ed. dtx is defined after the ini- tialization block is read. read/write accessible only when stop or spnd bits are set. 0 drx disable receiver. if this bit is set, the pcnet-isa ii controller will not access the receive descriptor ring and, therefore, all receive frame data are ignored. drx = ? 0" will set rxon bit (csr0.5) after strt (csr0.1) is asserted. drx is defined after the initialization block is read. read/write accessible only when stop or spnd bits are set. csr16: initialization block address lower bit name description 15-0 iadr lower 16 bits of the address of the initialization block. bit loca- tion 0 must be zero. this register is an alias of csr1. whenever this register is written, csr1 is updated with csr16 ? s contents. read/write accessible only when the stop or spnd bits are set. unaffected by reset. csr17: initialization block address upper bit name description 15-8 res reserved locations. written as zero and read as undefined. 7-0 iadr upper 8 bits of the address of the initialization block. bit loca- tions 15-8 must be written with zeros. this register is an alias of csr2. whenever this register is written, csr2 is updated with csr17 ? s contents. read/write accessible only when the stop or spnd bits are set. unaffected by reset. csr18-19: current receive buffer address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 crba contains the current receive buffer address to which the pc- net-isa ii controller will store in- coming frame data. read/write accessible only when stop or spnd bits are set. csr20-21: current transmit buffer address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 cxba contains the current transmit buffer address from which the pcnet-isa ii controller is trans- mitting. read/write accessible only when stop or spnd bits are set. loop intl mendecl loopback mode 0 x x non-loopback 1 0 x external loopback 11 0 internal loopback include mendec 11 1 internal loopback exclude mendec
106 am79c961a csr22-23: next receive buffer address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 nrba contains the next receive buffer address to which the pcnet-isa ii controller will store incoming frame data. read/write accessible only when stop or spnd bits are set. csr24-25: base address of receive ring bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 badr contains the base address of the receive ring. read/write accessible only when stop or spnd bits are set. csr26-27: next receive descriptor address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 nrda contains the next rdre address pointer. read/write accessible only when stop or spnd bits are set. csr28-29: current receive descriptor address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 crda contains the current rdre address pointer. read/write accessible only when stop or spnd bits are set. csr30-31: base address of transmit ring bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 badx contains the base address of the transmit ring. read/write accessible only when stop or spnd bits are set. csr32-33: next transmit descriptor address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 nxda contains the next tdre address pointer. read/write accessible only when stop or spnd bits are set. csr34-35: current transmit descriptor address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 cxda contains the current tdre address pointer. read/write accessible only when stop or spnd bits are set. csr36-37: next next receive descriptor address bit name description 31-0 nnrda contains the next next rdre address pointer. read/write accessible only when stop or spnd bits are set. csr38-39: next next transmit descriptor address bit name description 31-0 nnxda contains the next next tdre address pointer. read/write accessible only when stop or spnd bits are set. csr40-41: current receive status and byte count bit name description 31-24 crst current receive status. this field is a copy of bits 15:8 of rmd1 of the current receive descriptor. read/write accessible only when stop or spnd bits are set. 23-12 res reserved locations. written as zero and read as undefined.
am79c961a 107 11-0 crbc current receive byte count. this field is a copy of the bcnt field of rmd2 of the current receive descriptor. read/write accessible only when stop or spnd bits are set. csr42-43: current transmit status and byte count bit name description 31-24 cxst current transmit status. this field is a copy of bits 15:8 of tmd1 of the current transmit descriptor. read/write accessible only when stop or spnd bits are set. 23-12 res reserved locations. written as zero and read as undefined. 11-0 cxbc current transmit byte count. this field is a copy of the bcnt field of tmd2 of the current transmit descriptor. read/write accessible only when stop or spnd bits are set. csr44-45: next receive status and byte count bit name description 31-24 nrst next receive status. this field is a copy of bits 15:8 of rmd1 of the next receive descriptor. read/write accessible only when stop or spnd bits are set. 23-12 res reserved locations. written as zero and read as undefined. 11-0 nrbc next receive byte count. this field is a copy of the bcnt field of rmd2 of the next receive descriptor. read/write accessible only when stop or spnd bits are set. csr46: poll time counter bit name description 15-0 poll poll time counter. this counter is incriminated by the pcnet-isa ii controller microcode and is used to trigger the descriptor ring polling operation of the pc- net-isa ii controller. read/write accessible only when stop or spnd bits are set. csr47: polling interval bit name description 31-16 res reserved locations. written as zero and read as undefined. 15-0 pollint polling interval. this register contains the time that the pc- net-isa ii controller will wait be- tween successive polling operations. the pollint value is expressed as the two ? s com- plement of the desired interval, where each bit of pollint rep- resents one-half of an xtal1 period of time. pollint[3:0] are ignored. (polint[16] is implied to be a one, so pollint[15] is significant, and does not repre- sent the sign of the two ? s complement pollint value.) the default value of this register is 0000. this corresponds to a polling interval of 32,768 xtal1 periods. the polint value of 0000 is created during the micro- code initialization routine, and therefore might not be seen when reading csr47 after reset. if the user desires to program a value for pollint other than the default, then the correct procedure is to first set init only in csr0. then, when the initial- ization sequence is complete, the user must set stop in csr0. then the user may write to csr47 and then set strt in csr0. in this way, the default value of 0000 in csr47 will be overwritten with the desired user value. read/write accessible only when stop or spnd bits are set. csr48-49: temporary storage bit name description 31-0 tmp0 temporary storage location. read/write accessible only when stop or spnd bits are set. csr50-51: temporary storage bit name description 31-0 tmp1 temporary storage location.
108 am79c961a read/write accessible only when stop or spnd bits are set. csr52-53: temporary storage bit name description 31-0 tmp2 temporary storage location. read/write accessible only when stop or spnd bits are set. csr54-55: temporary storage bit name description 31-0 tmp3 temporary storage location. read/write accessible only when stop or spnd bits are set. csr56-57: temporary storage bit name description 31-0 tmp4 temporary storage location. read/write accessible only when stop or spnd bits are set. csr58-59: temporary storage bit name description 31-0 tmp5 temporary storage location. read/write accessible only when stop or spnd bits are set. csr60-61: previous transmit descriptor address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 pxda contains the previous tdre address pointer. the pcnet-isa ii controller has the capability to stack multiple transmit frames. read/write accessible only when stop or spnd bits are set. csr62-63: previous transmit status and byte count bit name description 31-24 pxst previous transmit status. this field is a copy of bits 15:8 of tmd1 of the previous transmit descriptor. read/write accessible only when stop or spnd bits are set. 23-12 res reserved locations. written as zero and read as undefined. accessible only when stop bit is set. 11-0 pxbc previous transmit byte count. this field is a copy of the bcnt field of tmd2 of the previous transmit descriptor. read/write accessible only when stop or spnd bits are set. csr64-65: next transmit buffer address bit name description 31-24 res reserved locations. written as zero and read as undefined. 23-0 nxba contains the next transmit buffer address from which the pc- net-isa ii controller will transmit an outgoing frame. read/write accessible only when stop or spnd bits are set. csr66-67: next transmit status and byte count bit name description 31-24 nxst next transmit status. this field is a copy of bits 15:8 of tmd1 of the next transmit descriptor. read/write accessible only when stop or spnd bits are set. 23-12 res reserved locations. written as zero and read as undefined. accessible only when stop bit is set. 11-0 nxbc next transmit byte count. this field is a copy of the bcnt field of tmd2 of the next transmit descriptor. read/write accessible only when stop or spnd bits are set.csr68-69: transmit status temporary storage bit name description 31-0 xstmp transmit status temporary storage location. read/write accessible only when stop or spnd bits are set.
am79c961a 109 csr70-71: temporary storage bit name description 31-0 tmp8 temporary storage location. read/write accessible only when stop or spnd bits are set. csr72: receive ring counter bit name description 15-0 rcvrc receive ring counter location. contains a two ? s complement binary number used to number the current receive descriptor. this counter interprets the value in csr76 as pointing to the first descriptor; a two ? s complement value of -1 (ffffh) corresponds to the last descriptor in the ring. read/write accessible only when stop or spnd bits are set. csr74: transmit ring counter bit name description 15-0 xmtrc transmit ring counter location. contains a two ? s complement binary number used to number the current transmit descriptor. this counter interprets the value in csr78 as pointing to the first descriptor; a two ? s complement value of -1 (ffffh) corresponds to the last descriptor in the ring. read/write accessible only when stop or spnd bits are set. csr76: receive ring length bit name description 15-0 rcvrl receive ring length. contains the two ? s complement of the receive descriptor ring length. this register is initialized during the pcnet-isa ii controller initial- ization routine based on the value in the rlen field of the ini- tialization block. this register can be manually altered; the actual receive ring length is defined by the current value in this register. read/write accessible only when stop or spnd bits are set. csr78: transmit ring length bit name description 15-0 xmtrl transmit ring length. contains the two ? s complement of the transmit descriptor ring length. this register is initialized during the pcnet-isa ii controller initial- ization routine based on the value in the tlen field of the ini- tialization block. this register can be manually altered; the actual transmit ring length is defined by the current value in this register. read/write accessible only when stop or spnd bits are set. csr80: burst and fifo threshold control bit name description 15-14 res reserved locations. read as ones. written as zero. 13-12rcvfw[1:0] receive fifo watermark. rcvfw controls the point at which isa bus receive dma is requested in relation to the num- ber of received bytes in the receive fifo. rcvfw specifies the number of bytes which must be present (once the frame has been verified as a non-runt) before receive dma is request- ed. note however that, if the net- work interface is operating in half-duplex mode, in order for receive dma to be performed for a new frame, at least 64 bytes must have been received. this effectively avoids having to react to receive frames which are runts or suffer a collision during the slot time (512 bit times). if the runt packet accept feature is enabled, receive dma will be requested as soon as either the rcvfw threshold is reached, or a complete valid receive frame is detected (regardless of length). rcvfw is set to a value of 10b (64 bytes) after reset. read/write accessible only when stop or spnd bits are set.
110 am79c961a . 11-10xmtsp[1:0]transmit start point. xmtsp controls the point at which preamble transmission attempts commence in relation to the number of bytes written to the transmit fifo for the current transmit frame. when the entire frame is in the fifo, transmis- sion will start regardless of the value in xmtsp. xmtsp is given a value of 10b (64 bytes) after reset. regardless of xmtsp, the fifo will not inter- nally over-write its data until at least 64 bytes (or the entire frame if <64 bytes) have been transmitted onto the network. this ensures that for collisions within the slot time window, transmit data need not be re-written to the transmit fifo, and retries will be handled autonomously by the mac. this bit is read/write accessible only when the stop or spnd bits are set. 9-8 xmtfw[1:0] transmit fifo watermark. xmtfw specifies the point at which transmit dma stops, based upon the number of write cycles that could be performed to the transmit fifo without fifo overflow. transmit dma is allowed at any time when the number of write cycles specified by xmtfw could be executed without causing transmit fifo overflow. xmtfw is set to a value of 00b (8 cycles) after hardware reset. read/write accessible only when stop or spnd bits are set. 7-0 dmabr dma burst register. this reg- ister contains the maximum allowable number of transfers to system memory that the bus interface will perform during a single dma cycle. the burst register is not used to limit the number of transfers during descriptor transfers. a value of zero will be interpreted as one transfer. during reset a value of 16 is loaded in the burst register. if dmaplus (csr4.14) is set, the dma burst register is disabled. when the bus activity timer register (csr82: dmabat) is enabled, the pcnet-isa ii con- troller will relinquish the bus when either the time specified in dmabat has elapsed or the number of transfers specified in dmabr have occurred or no more pending operation left to be performed. read/write accessible only when stop or spnd bits are set. csr82: bus activity timer bit name description 15-0 dmabat bus activity timer. if the timer bit in csr4 is set, this register contains the maximum allowable time that the pcnet-isa ii con- troller will take up on the system bus during fifo data transfers in each bus mastership period. the dmabat starts counting upon receipt of dack from the host system. the dmabat reg- ister does not limit the number of transfers during descriptor transfers. a value of zero will limit the pc- net-isa ii controller to one bus cycle per mastership period. a non-zero value is interpreted as an unsigned number with a res- olution of 100 ns. for instance, a value of 51 s would be pro- grammed with a value of 510. when the timer bit in csr4 is set, dmabat is enabled and must be initialized by the user. rcvfw[1:0] bytes received 00 16 01 32 10 64 11 reserved xmtsp[1:0] bytes written 00 4 01 16 10 64 11 112 xmtfw[1:0] write cycles 00 8 01 16 10 32 11 reserved xmtfw[1:0] write cycles
am79c961a 111 the dmabat register is unde- fined until written. when the bus activity timer register (csr82: dmabat) is enabled, the pcnet-isa ii con- troller will relinquish the bus when either the time specified in dmabat has elapsed or the number of transfers specified in dmabr have occurred or no more pending operation left to be performed. when entst (csr4.15) is asserted, all writes to this register will automatically perform a decrement cycle. read/write accessible only when stop or spnd bits are set. csr84-85: dma address bit name description 31-0 dmaba dma address register. this register contains the address of system memory for the current dma cycle. the bus interface unit controls the address register by issuing increment commands to increment the memory address for sequential operations. the dmaba register is undefined until the first pcnet-isa ii controller dma operation. this register has meaning only if the pcnet-isa ii controller is in bus master mode. read/write accessible only when stop or spnd bits are set. csr86: buffer byte counter bit name description 15-12 res reserved, read and written with ones. 11-0 dmabc dma byte count register. contains the two ? s comple- ment of the current size of the remaining transmit or receive buffer in bytes. this register is incriminated by the bus inter- face unit. the dmabc register is undefined until written. read/write accessible only when stop or spnd bits are set. csr88-89: chip id bit name description 31-28 version. this 4-bit pattern is silicon revision dependent. 27-12 part number. the 16-bit code for the pcnet-isa ii controller is 0010001001100001b (2261h). 11-1 manufacturer id. the 11-bit manufacturer code for amd is 00000000001b. this code is per the jedec publication 106-a. 0 always a logic 1. this register is exactly the same as the chip id register in the jtag description. this register is readable only when stop or spnd bits are set. csr92: ring length conversion bit name description 15-0 rcon ring length conversion regis- ter. this register performs a ring length conversion from an encoded value as found in the initialization block to a two ? s complement value used for internal counting. by writing bits 15 ? 12 with an encoded ring length, a two ? s comple- mented value is read. the rcon register is undefined until written. read/write accessible only when stop or spnd bits are set. csr94: transmit time domain reflectometry count bit name description 15-10 res reserved locations. read and written as zero. 9-0 xmttdr time domain reflectometry reflects the state of an internal counter that counts from the start of transmission to the occurrence of loss of carrier. tdr is incriminated at a rate of 10 mhz. read accessible only when stop or spnd bits are set. write operations are ignored. xmttdr is cleared by reset.
112 am79c961a csr96-97: bus interface scratch register 0 bit name description 31-0 scr0 this register is shared between the buffer management unit and the bus interface unit. all descriptor data communica- tions between the biu and bmu are written and read through scr0 and scr1 registers. the scr0 register is undefined until written. read/write accessible only when stop or spnd bits are set. csr98-99: bus interface scratch register 1 bit name description 31-0 scr1 this register is shared between the buffer management unit and the bus interface unit. all descriptor data communica- tions between the biu and bmu are written and read through scr0 and scr1 registers. read/write accessible only when stop or spnd bits are set. csr104-105: swap bit name description 31-0 swap this register performs word and byte swapping depending upon if 32-bit or 16-bit internal write operations are performed. this register is used internally by the biu/bmu as a word or byte swapper. the swap register can perform 32-bit operations that the pc can not; the register is externally accessible for test reasons only. csr104 holds the lower 16 bits and csr105 holds the upper 16 bits. the swap function is defined as follows: read/write accessible only when stop or spnd bits are set. csr108-109: buffer management scratch bit name description 31-0 bmscr the buffer management scratch register is used for assembling receive and transmit status. this register is also used as the primary scan register for buffer management test modes. bmscr register is undefined until written. read/write accessible only when stop bit is set. csr112: missed frame count bit name description 15-0 mfc counts the number of missed frames. this register is always readable and is cleared by stop. a write to this register performs an increment when the entst bit in csr4 is set. when mfc is all 1 ? s (65535) and a missed frame occurs, mfc increments to 0 and sets mfc0 bit (csr4.9). csr114: receive collision count bit name description 15-0 rcvcc counts the number of receive collisions seen, regular and late. this register is always readable and is cleared by stop. a write to this register performs an increment when the entst bit in csr4 is set. when rcvcc is all 1 ? s (65535) and a receive collision occurs, rcvcc increments to 0 and sets rcvcc0 bit (csr4.5) csr124: buffer management unit test bit name description this register is used to place the bmu/biu into various test modes to support test/debug. this register is writeable when the entst bit in csr4 is set. 15-5 res reserved locations. written as zero and read as undefined. 4 gpsien this mode places the pcnet-isa ii controller in the gpsi mode. internal write operation swap register result 32-bit word src[31:16] swap[15:0] src[15:0] swap[31:16] lower 16-bit (csr104) src[15:8] swap[7: 0] src[7:0] swap[15:8]
am79c961a 113 this mode will reconfigure the external address pins so that the gpsi port is exposed. this allows bypassing the mendec- tmau logic. this bit should only be set if the external logic sup- ports gpsi operation. damage to the device may occur in a non-gpsi configuration. refer to the gpsi section. 3 rpa runt packet accept. this bit forces the core receive logic to accept runt packets. this bit allows for faster testing. 2-0 res for test purposes only. reserved locations. written as zero and read as undefined.
114 am79c961a isa bus configuration registers the isa bus data port (idp) allows access to registers which are associated with the isa bus. these registers are called isa bus configuration registers (isacsrs), and are indexed by the value in the register address port (rap). the table below defines the isacsrs which can be accessed. all registers are 16 bits. the ? default ? value is the value in the register after reset and is hexadecimal.refer to the section ? leds ? for in- formation on led control logic. isacsr0: master mode read active/sram data port when in the bus master mode: bit name description 15-4 res reserved locations. written as zero and read as undefined. 3-0 msrda master mode read active time. this register is used to tune the memr command signal active time when the pcnet-isa ii is in the bus master mode. the value stored in msrda defines the number of 50 ns periods that the command signal is active. the default value of 5h indicates 250ns pulse widths. a value of 0 should not be used and may result in no command assertion. when in the bus slave, programmed i/o architecture mode: 15-0 sramdp sram data port. this register serves as a data port for access- ing the sram when the pc- net-isa ii is in the bus slave, programmed i/o architecture mode. accesses to this port are directed to the sram location that is addressed by the sramap register (isacsr1). word accesses and byte accesses to the even byte (least significant bits) are allowed. byte accesses to the odd byte are not allowed except when they are performed automatically by motherboard logic as discussed in the bus cycles (hardware) section. read and write accesses to this register will have the side effect that the sramap register (isacsr1) will incre- ment by 1 or 2 depending on whether a byte or word access, respectively, is performed. isacsr1: master mode write active/sram address pointer when in the bus master mode: bit name description 15-4 res reserved locations. written as zero and read as undefined. 3-0 mswra master mode write active time. this register is used to tune the memw command signal active time when the pcnet-isa ii is in the bus master mode. the value stored in mswra defines the number of 50 ns periods that the command signal is active. the default value of 5h indicates 250ns pulse widths. a value of 0 should not be used and may result in no command assertion. when in the bus slave, programmed i/o architecture mode: 15-0 sramap sram address pointer. this register functions as an address pointer for accessing the sram when the pcnet-isa ii is in the bus slave, programmed i/o architecture mode. accesses to the sramdp (isacsr0) regis- ter are directed to the sram location that is addressed by this register. this register is auto- isacsr mnemonic default name 0 msrda 0005h master mode read active 1 mswra 0005h master mode write active 2 mc 0002h miscellaneous configuration 3 ec 8000h* eeprom configuration 4 led0 0000h link integrity 5 led1 0084h default: rcv 6 led2 0008h default: rcvpol 7 led3 0090h default: xmt 8 sc 0000h software configuration (read-only register) 9 dup 0000h default: half duplex this value can be 0000h for systems that do not support eeprom option.
am79c961a 115 matically incriminated by 1 or 2 when byte or word accesses, respectively, are performed to the sramdp register (isacsr0). isacsr2: miscellaneous configuration 1 bit name description 15 mode_status mode status. this is a read-only register which indicates whether the pcnet-isa ii is configured in slave mode. a set condition indi- cates slave mode while a clear condition indicates bus-master condition. 14 tmau_loope 10base-t external loop back enable. this bit is usable only when 10base-t is selected and pcnet-isa ii is in external loop back. external loop back is set during initialization via the mode register. when tmau_loope is set, a board level test is enabled via a loop back clip which ties the 10base-t rj45 transmit pair to the receiver pair. this will test all external components (i.e. trans- formers, resistors, etc.) of the 10base-t path. tmau_ loope assertion is not suitable for live network tests. when tmau_loope is deasserted, default condition, external loop back in 10base-t is allowed. 13 piosel programmed i/o select. when operating in the bus slave mode with this bit reset to zero, a shared memory implementation is selected and the local sram is accessible through memory cycles on the isa bus interface. when operating in the bus slave mode with this bit set to one, a programmed i/o implementa- tion is selected and the local sram is accessible through i/o cycles on the isa bus interface. refer to the shared memory and programmed i/o sections for details on these two architecture schemes. when operating in the bus master mode, this bit has no effect. piosel is reset to zero. 12 slot_id slot identification. this is a read-only register bit which indi- cates if pcnet-isa ii is either in an 16 or 8 bit slot. reading a one indicates an 8 bit slot. zero indi- cates a 16-bit slot. (slot_id bit is not valid after the init bit is set in csr0.) 11 isa_protect isa protect. when set, the isacsr ? s 0 ? 2 and 4 ? 9 are protected from being written over by software drivers. when isa_ protect is cleared, isacsr ? s 0 ? 2 and 4 ? 9 are allowed to be written over by software and reset by reading the software reset i/o location. (default is zero) 10 eisa_decode eisa decode. this control bit allows eisa product identifier reg- isters 12-bit decode xc80 - xc83 (4 bytes). default is zero. 9 p&p_act plug and play active. when this bit is set, pcnet-isa ii will become active after serially reading the eeprom. if check sum failure exist, pcnet-isa ii will not become active and alternate access method to plug and play registers will occur. default is zero. 8 apwen address prom write enable. it is reset to zero by reset. when asserted, this pin allows write access to the internal address prom ram. apwen is used also to protect the flash device from write cycles. when pro- gramming of the flash device is required, the apwen bit needs to be set. when reset, this pin protects the internal address prom ram, and external flash device from being overwritten. 7 eisa_lvl eisa level. this bit is a read-only register. it indicates if the level or edge sensitive inter- rupts have been selected. a set condition indicates level sensi- tive interrupts. a clear condition indicates isa edge. 6 dsdbus disable staggered data bus. when this bit is a zero, the data bus driver timing is staggered from the address bus driver timing in bus master mode. when this bit is a one, the data bus is not staggered. it is similar to the pcnet-isa (am79c960) timing. this bit is reset to zero. for most applications, this bit should not have to be set. 5 10base5_sel 10base5 select. when set, this bit inverts the polarity of the dx- cvr pin only when the aui port
116 am79c961a is active. when the 10base5_sel bit is set and the aui port is active, the dxcvr is driven such that an external dc-dc converter will be disabled . the actual polarity of the dxcvr pin is determined by the dxcvrp bit in pnp register 0xf0. when the 10base-t port is active, this bit has no effect. 10base5_sel is reset to zero. 4 isainact isainact allows for reduced inactive timing appropriate for modern isa machines. isainact is cleared when reset is assert- ed. when isainact is a zero, tmmr3 and tmmw3 parameters are nominally 200 ns, which is compatible with eisa system. when isainact is set by writing a one, tmmr3 and tmmw3 are nominally set to 100 ns. 3 eadisel eadi select. enables eadi match mode. when eadi mode is selected, the pins named led1 , led2 , and led3 change in function while led0 continues to indicate 10base-t link status. 2 awake auto-wake. if awake = ? 1", the 10base-t receive circuitry is active during sleep and listens for link pulses. led0 indicates link status and goes active if the 10base-t port comes out of ? link fail ? state. this led0 pin can be used by external circuitry to re-enable the pcnet-isa ii controller and/or other devices. when awake = ? 0", the au- to-wake circuity is disabled. this bit only has meaning when the 10base-t network interface is selected. 1,0 medsel media select. it was previously defined as asel (auto select) and xmausel (external mau select) in the pcnet-isa. they are now combined together and defined to be software compatible with asel and xmausel in the pcnet-isa (am79c960). isacsr3: eeprom configuration bit name description 15 ee_valid eeprom valid. this bit is a read-only register. when a one is read, ee_prom has a valid checksum. the sum of the total bytes reads should equals ff hex. when a zero is read, check- sum failed, or shftbusy pin was sampled with a zero which indicates no eeprom present. 14 ee_load eeprom load. when written with a one, the device will load the eeprom into the pc- net-isa ii, performing self con- figuration. this command must be last write to isacsr3 regis- ter. pcnet-isa ii will not respond to any slave commands while loading the eeprom register. ee_load will be reset with a zero after eeprom is read. it takes approximately, 1.4 ms for serial eeprom load process to complete. 13 ? 5 n/a reserved. read and written as zeros. 4 ee_en eeprom enable. when ee_en is written with a one, the lower three bits of prdb becomes sk, di and do, respectively. eecs and shfbusy are controlled by the software select bits. this bit must be written with a one to write to or read from the ee- prom. pcnet-isa ii should be in the stop state when ee_en is written. when ee_en is cleared, di/do, sk, eecs and shfbusy have no control. 3 shfbusy shift busy. shfbusy allows for the control of the shfbusy pin. when a one is written, shfbusy goes high provided ee_en is a 1. when a zero is written, shf- busy is held to a zero. when ee_en is cleared, shfbusy will maintain the last value pro- grammed. (refer to bit 4 above, led eadi function 1sf/bd 2srd 3 srdclk medsel (1:0) function 0 0 software select (mode reg, csr15) 0 1 10base-t port 1 0 auto selection (default) 1 1 aui port
am79c961a 117 ee_en, for detailed use of this bit). 2 eecs eeprom chip select. eecs asserts the chip select to the serial eeprom. (refer to bit 4 above, ee_en, for detailed use of this bit). 1 sk serial shift clock. sk controls the sk input to the serial ee- prom and the optional external shift logic. (refer to bit 4 above, ee_en, for detailed use of this bit). 0 di/do serial shift data in and serial shift data out. when written, this bit controls the di input of the serial eeprom. when read, this bit represents the do value of the serial eeprom. (refer to bit 4 above, ee_en, for detailed use of this bit). isacsr4: led0 status (link integrity) bit name description isacsr4 is a non-programm- able register that uses one bit to reflect the status of the led0 pin. this pin defaults to twisted pair mau link status (lnkst) and is not programmable. 15 lnkst 10base-t link status. lnkst is a read-only bit that indicates whether the link status led is asserted. when lnkst is read as zero, the link status led is not asserted. when lnkst is read as one, the link status led is asserted, indicating good 10base-t link integrity. note that the lnkst led is masked if the 10base-t port is operating in full duplex mode, auifd (isacsr9, bit 1) is cleared, and any one of the fdlse bits is set in isacsr5, 6, or 7. hence, an adapter card with a 10base2 port (through the aui port) and a 10base-t port that can be software enabled for half or full duplex operation can have a half duplex link status led and a full duplex link status led in which only one will be allowed on, depending on if fden (isacsr9, bit 0) is set. 14-0 resreserved locations. written as zero, read as undefined. 14-0 res reserved locations. written as zero, read as undefined. isacsr5: led1 status bit name description isacsr5 controls the function(s) that the led1 pin displays. multi- ple functions can be simulta- neously enabled on this led pin. the led display will indicate the logical or of the enabled func- tions. isacsr5 defaults to receive status (rcv) with pulse stretcher enabled (pse = 1) and is fully programmable. 15 ledout indicates the current (non- stretched) state of the function(s) generated. read only. 14-10 res reserved locations. read and written as zero. 9 mp magic packet led enable. when set, the led output will be asserted to indicate that a magic packet has been received. 8 fdlse full duplex link status enable. indicates the full duplex link test status. when this bit is set, a value of one is passed to the ledout signal when the pc- net-isa ii is functioning in a link pass state with full duplex ca- pability. when the pcnet-isa ii is not functioning in a link pass state with full duplex capability, a value of zero is passed to the ledout signal. when the 10base-t port is active, a value of one is passed to the ledout signal whenever the link test function (described in the t-mau section) detects a link pass state and the fden (isacsr9, bit 0) bit is set. when the aui port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the aui port is enabled (both fden and auifd bits in isacsr9 are set to one). when the gpsi port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the gpsi port is enabled (fden bit in isacsr9 is set to one). 7 pse pulse stretcher enable. extends the led illumination for each enabled function occurrence.
118 am79c961a 0 is disabled, 1 is enabled. 6 res reserved locations. read and written as zero. 5 rcvaddm receive address match. this bit when set allows for led control of only receive packets which match internal address match. 4 xmt e enable transmit status signal. indicates pcnet-isa ii controller transmit activity. 0 disables the signal, 1 enables the signal. 3 rvpol e enable receive polarity signal. enables led pin assertion when receive polarity is correct on the 10base-t port. clearing the bit indicates this function is to be ignored. 2 rcv e enable receive status signal. indicates receive activity on the network. 0 disables the signal, 1 enables the signal. 1 jab e enable jabber signal. indicates the pcnet-isa ii controller is jab- bering on the network. 0 disables the signal, 1 enables the signal. 0 col e enable collision signal. indi- cates collision activity on the network. 0 disables the signal, 1 enables the signal. isacsr6: led2 status bit name description isacsr6 controls the func- tion(s) that the led2 pin dis- plays. multiple functions can be simultaneously enabled on this led pin. the led display will indicate the logical or of the enabled functions. isacsr6 defaults to twisted pair mau receive polarity (rcvpol) with pulse stretcher enabled (pse = 1) and is fully program- mable. 15 ledout indicates the current (non- stretched) state of the func- tion(s) generated. read only. 14 ledxor this bit when set causes led2 to be an active high signal when asserted. when this bit is cleared, led2 will be active low when asserted. note: this bit when used in conjunction with the rvpole bit (bit 3) of isacsr6 can be used to create a ? polarity bad ? led.) 13-10 res reserved locations. read and written as zero. 9 mp magic packet led enable. when set, the led output will be asserted to indicate that a magic packet has been received. 8 fdlse full duplex link status enable. indicates the full duplex link test status. when this bit is set, a value of one is passed to the ledout signal when the pc- net-isa ii is functioning in a link pass state with full duplex ca- pability. when the pcnet-isa ii is not functioning in a link pass state with full duplex capability, a value of zero is passed to the ledout signal. when the 10base-t port is active, a value of one is passed to the ledout signal whenever the link test function (described in the t-mau section) detects a link pass state and the fden (isacsr9, bit 0) bit is set. when the aui port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the aui port is enabled (both fden and auifd bits in isacsr9 are set to one). when the gpsi port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the gpsi port is enabled (fden bit in isacsr9 is set to one). 7 pse pulse stretcher enable. extends the led illumination for each enabled function occurrence. 0 is disabled, 1 is enabled. 6 res reserved locations. read and written as zero. 5 rcvaddm receive address match. this bit when set allows for led control rvpole ledxor result 0x 10base-t polarity function ignored 10 led2 pin low with ? good ? 10base-t polarity (led on) 11 led2 pin high with ? good ? 10base-t polarity (led off)
am79c961a 119 of only receive packets that match internal address match. 4 xmt e enable transmit status signal. indicates pcnet-isa ii controller transmit activity. 0 disables the signal, 1 enables the signal. 3 rvpol e enable receive polarity signal. enables led pin assertion when receive polarity is correct on the 10base-t port. clearing the bit indicates this function is to be ignored. 2 rcv e enable receive status signal. indicates receive activity on the network. 0 disables the signal, 1 enables the signal. 1 jab e enable jabber signal. indicates the pcnet-isa ii controller is jab- bering on the network. 0 disables the signal, 1 enables the signal. 0 col e enable collision signal. indi- cates collision activity on the network. 0 disables the signal, 1 enables the signal. isacsr7: led3 status bit name description isacsr7 controls the function(s) that the led3 pin displays. multi- ple functions can be simulta- neously enabled on this led pin. the led display will indicate the logical or of the enabled func- tions. isacsr7 defaults to transmit status (xmt) with pulse stretcher enabled (pse = 1) and is fully programmable. 15 ledout indicates the current (non- stretched) state of the func- tion(s) generated. read only. 14-10 res reserved locations. read and written as zero. 9 mp magic packet led enable. when set, the led output will be asserted to indicate that a magic packet has been received. 8 fdlse full duplex link status enable. indicates the full duplex link test status. when this bit is set, a value of one is passed to the ledout signal when the pc- net-isa ii is functioning in a link pass state with full duplex capa- bility. when the pcnet-isa ii is not functioning in a link pass state with full duplex capability, a val- ue of zero is passed to the ledout signal. when the 10base-t port is active, a value of one is passed to the ledout signal whenever the link test function (described in the t-mau section) detects a link pass state and the fden (isacsr9, bit 0) bit is set. when the aui port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the aui port is enabled (both fden and auifd bits in isacsr9 are set to one). when the gpsi port is active, a value of one is passed to the ledout signal whenever full duplex oper- ation on the gpsi port is enabled (fden bit in isacsr9 is set to one). 7 pse pulse stretcher enable. extends the led illumination for each enabled function occurrence. 0 is disabled, 1 is enabled. 6 res reserved locations. read and written as zero. 5 rcvaddm receive address match. this bit when set allows for led control of only receive packets that match internal address match. 4 xmt e enable transmit status signal. indicates pcnet-isa ii controller transmit activity. 0 disables the signal, 1 enables the signal. enable receive polarity signal. 3 rvpol e enables led pin assertion when receive polarity is correct on the 10base-t port. clearing the bit indicates this function is to be ignored. 2 rcv e enable receive status signal. indicates receive activity on the network. 0 disables the signal, 1 enables the signal. 1 jab e enable jabber signal. indicates the pcnet-isa ii controller is jab- bering on the network. 0 disables the signal, 1 enables the signal.
120 am79c961a 0 col e enable collision signal. indi- cates collision activity on the network. 0 disables the signal, 1 enables the signal. isacsr8: software configuration register (read-only register) isacsr9: miscellaneous configuration 2 bit name description 1 auifd aui full duplex. auifd controls whether full duplex operation on the aui port is enabled. auifd is only meaningful if fden (isacsr9, bit 0) is set to one. if the fden bit is zero, the aui port will always operate in half duplex mode. in addition, if fden is set to one but the auifd bit is reset to zero, the aui port will always operate in half duplex mode. if fden is set to one and auifd is set to one, full duplex operation on the aui port is enabled. auifd is read/write accessible always. it is reset to zero by the reset pin, and is unaffect- ed by reading the reset register or setting the stop bit. 0 fden full duplex enable. fden con- trols whether full duplex opera- tion is enabled. when fden is cleared, full duplex operation is not enabled and the pc- net-isa ii will always operate in the half duplex mode. when fden is set, the pcnet-isa ii will operate in full duplex mode when the 10base-t or gpsi port is enabled or when the aui port is enabled and the auifd (isacsr9, bit 1) bit is set. note that full duplex operation will not be enabled on the 10base-t port if dlnkst (csr15, bit 12) is set. fden is read/write accessible always. it is reset to zero by the reset pin, and is unaffect- ed by reading the reset register or setting the stop bit. initialization block the figure below shows the initialization block memory configuration. note that the initialization block must be based on a word (16-bit) boundary. rlen and tlen the tlen and rlen fields in the initialization block are 3 bits wide, occupying bits 15,14, and 13, and the value in these fields determines the number of transmit and receive descriptor ring entries (dre) which are used in the descriptor rings. their meaning is as follows: if a value other than those listed in the above table is desired, csr76 and csr78 can be written after initializa- tion is complete. see the description of the appropriate csrs. bit description 15-12 read-only image of sram(3:0) of pnp register 0x48-0x49. 11-8 read-only image of bpam(3:0) of pnp register 0x40-0x41. 7-4 read-only image of irqsel(3:0) of pnp register 0x70. 3 read only bit indicating whether the sram is activated as a memory resource. set when the shared memory is not activated as an isa memory resource. 2-0 read-only image of dmasel(2:0) of pnp register 0x74. address bits 15 ? 12 bits 11 ? 8 bits 7 ? 4 bits 3 ? 0 iadr+00 mode 15 ? 00 iadr+02 padr 15 ? 00 iadr+04 padr 31 ? 16 iadr+06 padr 47 ? 32 iadr+08 ladrf 15 ? 00 iadr+10 ladrf 31 ? 16 iadr+12 ladrf 47 ? 32 iadr+14 ladrf 63 ? 48 iadr+16 rdra 15 ? 00 iadr+18 rlen res rdra 23 ? 16 iadr+20 tdra 15 ? 00 iadr+22 tlen res tdra 23 ? 16 r/tlen # of dres 000 1 001 2 010 4 011 8 100 16 101 32 110 64 111 128
am79c961a 121 rdra and tdra tdra and rdra indicate where the transmit and receive descriptor rings, respectively, begin. each dre must be located on an 8-byte boundary. ladrf the logical address filter (ladrf) is a 64-bit mask that is used to accept incoming logical addresses. if the first bit in the incoming address (as transmitted on the wire) is a ? 1", the address is deemed logical. if the first bit is a ? 0", it is a physical address and is compared against the physical address that was loaded through the initialization block. a logical address is passed through the crc genera- tor, producing a 32-bit result. the high order 6 bits of the crc are used to select one of the 64 bit positions in the logical address filter. if the selected filter bit is set, the address is accepted and the frame is placed into memory. the logical address filter is used in multicast addressing schemes. the acceptance of the incoming frame based on the filter value indicates that the message may be intended for the node. it is the node ? s responsibility to determine if the message is actually intended for the node by comparing the destination address of the stored mes- sage with a list of acceptable logical addresses. if the logical address filter is loaded with all zeroes and promiscuous mode is disabled, all incoming logical addresses except broadcast will be rejected. the broadcast address, which is all ones, does not go through the logical address filter and is handled as follows: 7. if the disable broadcast bit is cleared, the broadcast address is accepted. 8. if the disable broadcast bit is set and promiscuous mode is enabled, the broadcast address is accepted. 9. if the disable broadcast bit is set and promiscous mode is disabled, the broadcast address is rejected. if external loopback is used, the fcs logic must be allocated to the receiver (by setting the dxmtfcs bit in csr15, and clearing the add_fcs bit in tmd1) when using multicast addressing. padr this 48-bit value represents the unique node address assigned by the ieee and used for internal address comparison. padr[0] is the first address bit transmit- ted on the wire, and must be zero. the six-hex-byte no- menclature used by the ieee maps to the pcnet-isa ii controller padr register as follows: the first byte com- prises padr[7:0], with padr[0] being the least signifi- cant bit of the byte. the second ieee byte maps to padr[15:8], again from lsbit to msbit, and so on. the sixth byte maps to padr[47:40], the lsbit being padr[40]. mode the mode register in the initialization block is copied into csr15 and interpreted according to the descrip- tion of csr15. . crc gen sel 47 1 0 31 26 0 63 0 64 mux match = 1: packet accepted match = 0: packet rejected 1 6 match logical address filter (ladrf) received message destination address 32-bit resultant crc address match logic 19364b-23
122 am79c961a receive descriptors the receive descriptor ring entries (rdres) are composed of four receive message fields (rmd0-3). together they contain the following information: the address of the actual message data buffer in user (host) memory the length of that message buffer status information indicating the condition of the buffer. the eight most significant bits of rmd1 (rmd1[15:0]) are collectively termed the status of the receive descriptor. rmd0 holds ladrf [15:0]. this is combined with hadr [7:0] in rmd1 to form the 24-bit address of the buffer pointed to by this descriptor table entry. there are no restrictions on buffer byte alignment or length. rmd1 bit name description 15 own this bit indicates that the descrip- tor entry is owned by the host (own=0) or by the pcnet-isa ii controller (own=1). the pcnet- isa ii controller clears the own bit after filling the buffer pointed to by the descriptor entry. the host sets the own bit after emp- tying the buffer. once the pc- net-isa ii controller or host has relinquished ownership of a buff- er, it must not change any field in the descriptor entry. 14 err err is the or of fram, oflo, crc, or buff. err is written by the pcnet-isa ii controller. 13 fram framing error indicates that the incoming frame con- tained a non-integer multiple of eight bits and there was an fcs error. if there was no fcs error on the incoming frame, then fram will not be set even if there was a non integer multiple of eight bits in the frame. fram is not valid in internal loopback mode. fram is valid only when enp is set and oflo is not. fram is written by the pc- net-isa ii controller. 12 oflo overflow error indicates that the receiver has lost all or part of the incoming frame, due to an inability to store the frame in a memory buffer before the inter- nal fifo overflowed. oflo is valid only when enp is not set. oflo is written by the pc- net-isa ii controller. 11 crc crc indicates that the receiver has detected a crc (fcs) error on the incoming frame. crc is valid only when enp is set and oflo is not. crc is written by the pcnet-isa ii controller. 10 buff buffer error is set any time the pcnet-isa ii controller does not own the next buffer while data chaining a received frame. this can occur in either of two ways: 1) the own bit of the next buffer is zero 2) fifo overflow occurred before the pcnet-isa ii controller polled the next descriptor if a buffer error occurs, an over- flow error may also occur inter- nally in the fifo, but will not be reported in the descriptor status entry unless both buff and oflo errors occur at the same time. buff is written by the pc- net-isa ii controller. 9 stp start of packet indicates that this is the first buffer used by the pcnet-isa ii controller for this frame. it is used for data chaining buffers. stp is written by the pcnet-isa ii controller in normal operation. in srpint mode (csr3.5 set to 1) this bit is written by the driver. 8 enp end of packet indicates that this is the last buffer used by the pcnet-isa ii controller for this frame. it is used for data chain- ing buffers. if both stp and enp are set, the frame fits into one buffer and there is no data chain- ing. enp is written by the pc- net-isa ii controller. 7-0 hadr the high order 8 address bits of the buffer pointed to by this descriptor. this field is writ- ten by the host and is not changed by the pcnet-isa ii controller. rmd2 bit name description 15-12 ones must be ones. this field is written by the host and
am79c961a 123 unchanged by the pcnet-isa ii controller. 11-0 bcnt buffer byte count is the length of the buffer pointed to by this descriptor, expressed as the two ? s complement of the length of the buffer. this field is written by the host and is not changed by the pcnet-isa ii controller. rmd3 bit name description 15-12 res reserved and read as zeros. 11-0 mcnt message byte count is the length in bytes of the received message, expressed as an un- signed binary integer. mcnt is valid only when err is clear and enp is set. mcnt is written by the pcnet-isa ii controller and cleared by the host. mcnt includes: dest + src + length + data + crc unless the auto strip on receive bit is set. in this case, the pad and crc are thrown away by the controller. transmit descriptors the transmit descriptor ring entries (tdres) are composed of four transmit message fields (tmd0-3). together they contain the following information: the address of the actual message data buffer in user or host memory the length of the message buffer status information indicating the condition of the buffer. the eight most significant bits of tmd1 (tmd1[15:8]) are collectively termed the status of the transmit descriptor. note that bit 13 of tmd1, which was formerly a reserved bit in the lance (am7990), is assigned a new meaning, add_fcs. tmd0 holds ladr [15:0]. this is combined with hadr [7:0] in tmd1 to form a 24-bit address of the buffer pointed to by this descriptor table entry. there are no restric- tions on buffer byte alignment or length. tmd1 bit name description 15 own this bit indicates that the descriptor entry is owned by the host (own=0) or by the pc- net-isa ii controller (own=1). the host sets the own bit after filling the buffer pointed to by the descriptor entry. the pcnet-isa ii controller clears the own bit after transmitting the contents of the buffer. both the pcnet-isa ii controller and the host must not alter a descriptor entry after it has relinquished ownership. 14 err err is the or of uflo, lcol, lcar, or rtry. err is written by the pcnet-isa ii controller. this bit is set in the current de- scriptor when the error occurs, and therefore may be set in any descriptor of a chained buffer transmission. 13 add_fcs add_fcs dynamically controls the generation of fcs on a frame by frame basis. it is valid only if the stp bit is set. when add_fcs is set, the state of dxmtfcs is ignored and trans- mitter fcs generation is activat- ed. when add_fcs = 0, fcs generation is controlled by dxmtfcs. add_fcs is written by the host, and unchanged by the pcnet-isa ii controller. this was a reserved bit in the lance (am7990). 12 more more indicates that more than one re-try was needed to trans- mit a frame. more is written by the pcnet-isa ii controller. this bit has meaning only if the enp or the err bit is set. 11 one one indicates that exactly one re-try was needed to transmit a frame. one flag is not valid when lcol is set. one is writ- ten by the pcnet-isa ii control- ler. this bit has meaning only if the enp or the err bit is set. 10 def deferred indicates that the pcnet-isa ii controller had to defer while trying to transmit a frame. this condition occurs if the channel is busy when the pcnet-isa ii controller is ready to transmit. def is written by the pcnet-isa ii controller. this bit has meaning only if the enp or err bits are set.
124 am79c961a 9 stp start of packet indicates that this is the first buffer to be used by the pcnet-isa ii con- troller for this frame. it is used for data chaining buffers. the stp bit must be set in the first buffer of the frame, or the pcnet-isa ii controller will skip over the descriptor and poll the next descriptor(s) until the own and stp bits are set. stp is written by the host and is not changed by the pcnet-isa ii controller. 8 enp end of packet indicates that this is the last buffer to be used by the pcnet-isa ii controller for this frame. it is used for data chaining buffers. if both stp and enp are set, the frame fits into one buffer and there is no data chaining. enp is written by the host and is not changed by the pcnet-isa ii controller. 7-0 hadr the high order 8 address bits of the buffer pointed to by this descriptor. this field is writ- ten by the host and is not changed by the pcnet-isa ii controller. tmd2 bit name description 15-12 ones must be ones. this field is written by the host and unchanged by the pcnet-isa ii controller. 11-0 bcnt buffer byte count is the length of the buffer pointed to by this descriptor, expressed as the two ? s complement of the length of the buffer. this is the number of bytes from this buffer that will be transmitted by the pcnet-isa ii controller. this field is written by the host and is not changed by the pcnet-isa ii controller. there are no minimum buffer size restrictions. zero length buffers are allowed for protocols which require it. tmd3 bit name description 15 buff buffer error is set by the pcnet-isa ii controller during transmission when the pc- net-isa ii controller does not find the enp flag in the current buffer and does not own the next buff- er. this can occur in either of two ways: 1) the own bit of the next buffer is zero. 2) fifo underflow occurred before the pcnet-isa ii controller obtained the next status byte (tmd1[15:8]). buff error will turn off the transmitter (csr0, txon = 0), if dxsuflo = 0 (bit 6 csr3). if a buffer error occurs, an underflow error will also occur. buff is not valid when lcol or rtry error is set during transmit data chaining. buff is written by the pcnet-isa ii controller. 14 uflo underflow error indi- cates that the transmitter has truncated a message due to data late from memory. uflo indicates that the fifo has emp- tied before the end of the frame was reached. upon uflo error, the transmitter is turned off (csr0, txon = 0), if dxsuflo = 0 (bit 6 csr3). uflo is written by the pcnet-isa ii controller. 13 res reserved bit. the pcnet-isa ii controller will write this bit with a ? 0". 12 lcol late collision indicates that a collision has occurred after the slot time of the channel has elapsed. the pcnet-isa ii con- troller does not re-try on late col- lisions. lcol is written by the pcnet-isa ii controller. 11 lcar loss of carrier is set in aui mode when the carrier is lost during an pcnet-isa ii con- troller- initiated transmission. the pcnet-isa ii controller does not stop transmission upon loss of carrier. it will continue to transmit the whole frame until done. lcar is written by the pcnet-isa ii controller. in 10base-t mode, lcar will be set when the t-mau is in link fail state. 10 rtry retry error indicates that the transmitter has failed after 16 attempts to successfully transmit a message, due to repeated collisions on the
am79c961a 125 medium. if drty = 1 in the mode register, rtry will set after one failed transmission at- tempt. rtry is written by the pcnet-isa ii controller. 09-00 tdr time domain reflectome- try reflects the state of an inter- nal pcnet-isa ii controller counter that counts at a 10 mhz rate from the start of a transmis- sion to the occurrence of a colli- sion or loss of carrier. this value is useful in determining the approximate distance to a cable fault. the tdr value is written by the pcnet-isa ii controller and is valid only if rtry is set. note that 10 mhz gives very low resolution and in general has not been found to be particularly useful. this feature is here primarily to maintain full compat- ibility with the lance.
126 am79c961a register summary ethernet controller registers (accessed via rdp port) rap addr symbol width user register comments 00 csr0 16-bit y pcnet-isa ii controller status 01 csr1 16-bit y lower iadr: maps to location 16 02 csr2 16-bit y upper iadr: maps to location 17 03 csr3 16-bit y mask register 04 csr4 16-bit y miscellaneous register 05 csr5 16-bit reserved 06 csr6 16-bit rxtx: rx/tx encoded ring lengths 07 csr7 16-bit reserved 08 csr8 16-bit y ladr0: ladrf[15:0] 09 csr9 16-bit y ladr1: ladrf[31:16] 10 csr10 16-bit y ladr2: ladrf[47:32] 11 csr11 16-bit y ladr3: ladrf[63:48] 12 csr12 16-bit y padr0: padr[15:0] 13 csr13 16-bit y padr1: padr[31:16] 14 csr14 16-bit y padr2: padr[47:32] 15 csr15 16-bit y mode: mode register 16-17 csr16 32-bit iadr: base address of init block 18-19 csr18 32-bit crba: current rcv buffer address 20-21 csr20 32-bit cxba: current xmt buffer address 22-23 csr22 32-bit nrba: next rcv buffer address 24-25 csr24 32-bit y badr: base address of rcv ring 26-27 csr26 32-bit nrda: next rcv descriptor address 28-29 csr28 32-bit crda: current rcv descriptor address 30-31 csr30 32-bit y badx: base address of xmt ring 32-33 csr32 32-bit nxda: next xmt descriptor address 34-35 csr34 32-bit cxda: current xmt descriptor address 36-37 csr36 32-bit next next receive descriptor address 38-39 csr38 32-bit next next transmit descriptor address 40-41 csr40 32-bit crbc: current rcv stat and byte count 42-43 csr42 32-bit cxbc: current xmt status and byte count 44-45 csr44 32-bit nrbc: next rcv stat and byte count 46 csr46 16-bit poll: poll time counter 47 csr47 32-bit y polling interval 48-49 csr48 32-bit tmp0: temporary storage 50-51 csr50 32-bit tmp1: temporary storage 52-53 csr52 32-bit tmp2: temporary storage 54-55 csr54 32-bit tmp3: temporary storage 56-57 csr56 32-bit tmp4: temporary storage 58-59 csr58 32-bit tmp5: temporary storage 60-61 csr60 32-bit pxda: previous xmt descriptor address 62-63 csr62 32-bit pxbc: previous xmt status and byte count
am79c961a 127 register summary ethernet controller registers (accessed via rdp port) note: although the pcnet-isa ii controller has many registers that can be accessed by software, most of these registers are intended for debugging and production testing purposes only. the registers with a "y" are the only registers that should be accessed by network software. rap addr symbol width user register comments 64-65 csr64 32-bit nxba: next xmt buffer address 66-67 csr66 32-bit nxbc: next xmt status and byte count 68-69 csr68 32-bit xstmp: xmt status temporary 70-71 csr70 32-bit rstmp: rcv status temporary 72 csr72 16-bit rcvrc: rcv ring counter 74 csr74 16-bit xmtrc: xmt ring counter 76 csr76 16-bit y rcvrl: rcv ring length 78 csr78 16-bit y xmtrl: xmt ring length 80 csr80 16-bit y dmabr: burst register 82 csr82 16-bit y dmabat: bus activity timer 84-85 csr84 32-bit dmaba: address register 86 csr86 16-bit dmabc: byte counter/register 88-89 csr88 32-bit y chip id register 92 csr92 16-bit rcon: ring length conversion register 94 csr94 16-bit xmttdr: transmit time domain reflectometry 96-97 csr96 32-bit scr0: biu scratch register 0 98-99 csr98 32-bit scr1: biu scratch register 1 104-105 csr104 32-bit swap:16-bit word/byte swap register 108-109 csr108 32-bit bmscr: bmu scratch register 112 csr112 16-bit y missed frame count 114 csr114 16-bit y receive collision count 124 csr124 16-bit y bmu test register 126 csr126 16-bit reserved
128 am79c961a register summary isacsr ? isa bus configuration registers (accessed via idp port) * this value can be 0000h for systems that do not support eeprom option i/o address offset rap addr mnemonic default name 0 msrda 0005h master mode read active 1 mswra 0005h master mode write active 2 mc 0002h miscellaneous configuration 3 ec 8000*h eeprom configuration 4 led0 0000h led0 status (link integrity) 5 led1 0084h led1 status (default: rcv) 6 led2 0008h led2 status (default: rcvpol) 7 led3 0090h led3 status (default: xmt) 8 sc 0000h software configuration (read-only register) 9 dup 0000h full/half duplex conditions (default: half duplex) offset #bytes register 0h 16 address prom 10h 2 rdp 12h 2 rap(shared by rdp and idp) 14h 2 reset 16h 2 idp
am79c961a 129 system application isa bus interface compatibility considerations although 8 mhz is now widely accepted as the standard speed at which to run the isa bus, many machines have been built which operate at higher speeds with non-stan- dard timing. some machines do not correctly support 16-bit i/o operations with wait states. although the pc- net-isa ii controller is quite fast, some operations still re- quire an occasional wait state. the pcnet-isa ii controller moves data through memory accesses, there- fore, i/o operations do not affect performance. by con- figuring the pcnet-isa ii controller as an 8-bit i/o device, compatibility with pc/at-class machines is obtained at virtually no cost in performance. to treat the pcnet-isa ii controller as an 8-bit software resource (for non-isa applications), the even-byte must be accessed first, followed by an odd-byte access. memory cycle timing is an area where some tradeoffs may be necessary. any slow down in a memory cycle translates directly into lower bandwidth. the pc- net-isa ii controller starts out with much higher band- width than most slave type controllers and should continue to be superior even if an extra 50 or 100 ns are added to memory cycles. the memory cycle active time is tunable in 50 ns incre- ments with a default of 250 ns. the memory cycle idle time defaults to 200 ns and can be reprogrammed to 100 ns. see register description for isacs42. most machines should not need tuning. the pcnet-isa ii controller is compatible with ne2100 and ne1500t software drivers. all the resources such as address prom, boot prom, rap, and rdp are in the same location with the same semantics. an addi- tional set of registers (isa csr) is available to config- ure on board resources such as isa bus timing and led operation. however, loopback frames for the pc- net-isa ii controller must contain more than 64 bytes of data if the runt packet accept feature is not enabled; this size limitation does not apply to lance (am7990) based boards such as the ne2100 and ne1500t. bus master bus master mode is the preferred mode for client appli- cations on pc/at or similar machines supporting 16-bit dma with its unsurpassed combination of high perfor- mance and low cost. shared memory the shared memory mode is recommended for file servers or other applications where there is very high, average or peak latency. the address compare circuit has the following func- tions. it receives the 7 la signals, generates memcs16 , and compares them to the desired shared memory and boot prom addresses. the logic latches the address compare result when bale goes inactive and uses the appropriate sa signals to generate smam and bpam . all these functions can be performed in one pal device. to operate in an 8-bit pc/xt environment, the la signals should have weak pull-down resistors con- nected to them to present a logic 0 level when not driven.
130 am79c961a d[0 ? 7] a[0 ? 15] do di sk cs org sd[0 ? 15] isa bus 16-bit system data 24-bit system address pcnet-isa ii controller boot prom eeprom v cc v cc prdb[2]/eedo prdb[1]/eedi prdb[0]/eesk prdb[0-7] sa[0 ? 19] la[17 ? 23] bpcs shfbusy ce oe eecs bus master block diagram plug and play compatible 19364b-24 sd[0 ? 15] sa[0] la[17 ? 23] d[0 ? 7] a[0 ? 4] sk di do cs eecs org d[0 ? 7] a[0 ? 15] we isa bus 24-bit system address pcnet-isa ii controller ieee address prom eeprom flash prdb[0]/eesk prdb[1]/eedi prdb[2]/eedo 16-bit system data v cc v cc irq15/ irq12/flashwe oe cs g bpcs prdb[0] shfbusy bus master block diagram plug and play compatible with flash support 19364b-25
am79c961a 131 a[0 ? 15] 2 1 0 v cc isa bus pcnet-isa ii controller boot prom sram eeprom prdb[2]/eedo prdb[1]/eedi prdb[0]/eesk do di sk ce oe d[0-7] a[0-15] d[0-7] we cs bpam smam sa[16] memcs16 external glue logic shfbusy clk sin 16-bit system data 24-bit system address srwe prab(0:15) la[17-23] v cc sroe bpcs prdb[0 ? 7] eecs sd[0 ? 15] sa[0 ? 15] smam shfbusy bpam cs oe org shared memory block diagram plug and play compatible 19364b-26
132 am79c961a optional address prom interface the suggested address prom is the am27ls19, a 32x8 device. apcs should be connected directly to the device ? s g input. boot prom interface the boot prom is a 8k ? 64k eprom. its oe pin should be tied to ground, and chip enable ce to bpcs to minimize power consumption at the expense of speed. shown below is a 27c128. higher density eproms place an address line on the pin that is defined for lower density eproms as the v pp (programming voltage) pin. for read only opera- tion on an eprom, the v pp pin can assume any logic level, as long as the voltage on the v pp pin does not exceed the programming voltage threshold (typically 7 v to 12 v). therefore, a socket with a 27512 pinout will also support 2764 and 27128 eprom devices. bpcs prdb[0 ? 7] org flash eeprom sram external glue logic eecs isa bus 24-bit system address pcnet-isa ii controller prdb[2]/eedo prdb[1]/eedi prdb[0]/eesk 16-bit system data prab[0-15] irq12/srcs v cc d[0-7] d[0-7] a[0-15] a[0-15] memcs16 sa[16] la[17-23] v cc srwe sroe bpam sram shfbusy we cs oe sin clk bpam sram shfbusy oe cs we do di sk cs sa[0 ? 19] sd[0 ? 15] shared memory block diagram plug and play compatible with flash memory support 19364b-27 27ls19 32 x 8 prom g a4 ? a0 q7 ? q0 address prom example 19364b-28
am79c961a 133 static ram interface (for shared memory only) the sram is an 8kx8 or 32kx8 device. the pcnet-isa ii controller can support 64 kbytes of sram address space. the pcnet-isa ii controller provides sroe and srwe outputs which can go directly to the oe and pins of the sram, respectively. the address lines are connected as described in the shared memory section and the data lines go to the private data bus. aui the pcnet-isa ii controller drives the aui through a set of transformers. the di and ci inputs should each be terminated with a pair of matched 39 ? or 40.2 ? resis- tors connected in series with the middle node bypassed to ground with a.01 f to 0.1 f capacitor. refer to the pcnet-isa technical manual (pid #16850b) for network interface design and refer to appendix a for a list of compatible aui isolation transformers. eeprom interface the suggested eeprom is the industry standard 93c56 2 kbit serial eeprom. this is used in the 16-bit mode to provide 128 x 16-bit eeprom locations to store configuration information as well as the plug and play information. 10base-t interface the diagram below shows the proper 10base-t network interface design. refer to the pcnet family technical manual (pid #18216a) for more design details, and refer to appendix a for a list of compatible 10base-t filter/ transformer modules. 27c128 16k x 8 eprom a13 ? a0 ce oe dq7 ? dq0 19364b-29 93c56 v cc eecs prdb2/eedo prdb1/eedi prdb0/eesk cs do di clk org boot prom example 19364b-30 xmt filter rcv filter rj45 connector filter & transformer module txp+ txd- txp- txd+ rxd+ rxd- pcnet-isa ii td+ td- rd+ rd- 1 2 3 6 61.9 422.0 61.9 422.0 100 1.21 k 1:1 1:1 controller 10base-t external components and hookup 19364b-31
134 am79c961a absolute maximum ratings storage temperature . . . . . . . . . . . . ? 65 c to +150 c ambient temperature . . . . . . . . . . . . . . . . . . . . . . . . . under bias . . . . . . . . . . . . . . . . . . . . . . . 0 c to +70 c supply voltage to avss or dv ss (av dd , dv dd ). . . . . . . . . . . ? 0.3 v to +6.0 v stresses above those listed under absolute maximum rat- ings may cause permanent device failure. functionality at or above these limits is not implied. exposure to absolute max- imum ratings for extended periods may affect device reliabil- ity. programming conditions may differ. operating ranges commercial (c) devices ambient temperature (t a ) . . . . . . . . . . . 0 c to+70 c industrial (i) devices ambient temperature (t a ) . . . . . . . . . ? 40 c to+85 c v cc supply voltages . . . . . . (av dd , dv dd ) 5 v 5% all inputs within the range : . . av ss ? 0.5 v v in av dd + 0.5 v, or dv ss ? 0.5 v v in dv dd + 0.5 v operating ranges define those limits between which the func- tionality of the device is guaranteed. dc characteristics (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) parameter symbol parameter description test conditions min max unit digital input voltage v il input low voltage 0.8 v v ih input high voltage 2.0 dv dd + 0.5 v digital output voltage v ol output low voltage 0.5 v v oh output high voltage (note 1) 2.4 v digital input leakage current i ix input leakage current v dd = 5 v, v in = 0 v (note 2) ? 10 10 a digital output leakage current i ozl output low leakage current (note 3) v out = 0 v ? 10 a i ozh output high leakage current (note 3) v out = v dd 10 a crystal input current v ilx xtal1 input low threshold voltage v in = external clock ? 0.5 0.8 v v ilhx xtal1 input high threshold voltage v in = external clock 3.5 v dd + 0.5 v i ilx xtal1 input low current v in = dv ss active ? 120 0 a sleep ? 10 +10 a i ihx xtal1 input high current v in = v dd active 0 120 a sleep 400 a attachment unit interface i iaxd input current at di+ and di ? av ss < v in < av dd ? 500 +500 a i iaxc input current at ci+ and ci ? av ss < v in < av dd ? 500 +500 a v aod differential output voltage |(do+) ? (do ? )| r l = 78 ? 630 1200 mv
am79c961a 135 dc characteristics (continued) parameter symbol parameter description test conditions min max unit attachment unit interface (continued) v aodoff transmit differential output idle voltage r l = 78 ? ? 40 +40 mv i aodoff transmit differential output idle current r l = 78 ? (note 4) ? 1+1ma v cmt transmit output common mode voltage r l = 78 ? 2.5 av dd v v odi do transmit differential output voltage imbalance r l = 78 ? (note 5) 25 mv v at h receive data differential input threshold (note 5) ? 35 35 mv v asq di and ci differential input threshold (squelch) ? 275 ? 160 mv v irdvd di and ci differential mode input voltage range ? 1.5 +1.5 v v icm di and ci input bias voltage i in = 0 ma av dd ? 3.0 av dd ? 1.0 v v opd do undershoot voltage at zero differential on transmit return to zero (etd) (note 5) ? 100 mv twisted pair interface i irxd input current at rxd av ss < v in < av dd ? 500 500 a r rxd rxd differential input resistance (note 5) 10 k ? v tivb rxd+, rxd ? open circuit input voltage (bias) i in = 0 ma av dd ? 3.0 av dd ? 1.5 v v tidv differential mode input voltage range (rxd ) av dd = +5 v ? 3.1 +3.1 v v tsq + rxd positive squelch threshold (peak) sinusoid 5 mhz f 10 mhz 300 520 mv v tsq ? rxd negative squelch threshold (peak) sinusoid 5 mhz f 10 mhz ? 520 ? 300 mv v ths+ rxd post-squelch positive threshold (peak) sinusoid 5 mhz f 10 mhz 150 293 mv v ths ? rxd post-squelch negative threshold (peak) sinusoid 5 mhz f 10 mhz ? 293 ? 150 mv v lt s q+ rxd positive squelch threshold (peak) lrt = 1 (note 6) 180 312 mv v lts q ? rxd negative squelch threshold (peak) lrt = 1 (note 6) ? 312 ? 180 mv v lth s + rxd post-squelch positive threshold (peak) lrt = 1 (note 6) 90 156 mv v lth s ? rxd post-squelch negative threshold (peak) lrt = 1 (note 6) ? 156 ? 90 mv
136 am79c961a dc characteristics (continued) 1. v oh does not apply to open-drain output pins. 2. i ix applies to all input only pins except di+ , ci+ , xtal1 and prdb[7:0]. 3. o zl applies to all three-state output pins and bi-directional pins, except prdb[7:0]. i ozh applies to pins prdb[7:0]. 4. correlated to other tested parameters ? not tested directly. 5. parameter not tested. 6. lrt is bit 9 of mode register (csr15) parameter symbol parameter description test conditions min max unit twisted pair interface (continued) v rxdth rxd switching threshold (note 5) ? 35 35 mv v txh txd and txp output high voltage dv ss = 0 v dv dd ? 0.6 dv dd v v txl txd and txp output low voltage dv dd = +5 v dv ss dv ss + 0.6 v v txi txd and txp differential output voltage imbalance ? 40 +40 mv v txoff txd and txp idle output voltage dv dd = +5 v ? 40 +40 mv r tx txd differential driver output impedance (note 5) 40 ? txp differential driver output impedance (note 5) 80 ? ieee 1149.1 (jtag) test port v il tck, tms, tdi 0.8 v v ih tck, tms, tdi 2.0 v v ol tdo i ol = 2.0 ma 0.4 v v oh tdo i oh = ? 0.4 ma 2.4 v i il tck, tms, tdi v dd = 5.5 v, v i = 0.5 v ? 200 a i ih tck, tms, tdi v dd =5.5 v, v i = 2.7 v ? 100 a i oz tdo 0.4 v < v out < v dd ? 10 +10 a power supply current i dd active power supply current xtal1 = 20 mhz 75 ma i ddcoma coma mode power supply current sleep active 200 a i ddsnooze snooze mode mall power supply current awake bit set active 10 ma
am79c961a 137 switching characteristics: bus master mode (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) parameter symbol parameter description test conditions min max unit input/output write timing t iow1 aen, sbhe , sa0 ? 9 setup to iow 10 ns t iow2 aen, sbhe ,sa0 ? 9 hold after iow 5ns t iow3 iow assertion 100 ns t iow4 iow inactive 55 ns t iow5 sd setup to iow 10 ns t iow6 sd hold after iow 10 ns t iow7 iochrdy delay from iow 0 35 ns t iow8 iochrdy inactive 125 ns t iow9 iochrdy to iow 0 ns input/output read timing t ior1 aen, sbhe , sa0 ? 9 setup to ior 15 ns t ior2 aen, sbhe , sa0 ? 9 hold after ior 5ns t ior3 ior inactive 55 ns t ior4 sd hold after ior 020ns t ior5 sd valid from ior 0110ns t ior6 iochrdy delay from ior 0 35 ns t ior7 iochrdy inactive 125 ns t ior8 sd valid from iochrdy ? 130 10 ns i/o to memory command inactive t iom1 iow /memw to (s )memr /ior 55 ns t iom2 (s )memr /ior to iow /memw 55 ns iocs16 timing t iocs1 aen, sbhe , sa0 ? 9 to iocs16 035ns t iocs2 aen, sbhe , sa0 ? 9 to iocs16 tristated 025ns master mode bus acquisition t mma1 ref inactive to dack 5ns t mma2 drq to dack 0ns t mma3 dack inactive 55 ns t mma4 dack to master 35 ns t mma5 master to active command, sbhe , sa0 ? 19, la17 ? 23 125 185 ns
138 am79c961a switching characteristics: bus master mode (continued) parameter symbol parameter description test conditions min max unit master mode bus release t mmbr1 command deassert to drq 45 65 ns t mmbr2 drq to dack 0ns t mmbr3 drq to master 40 60 ns t mmbr4 drq to command, sbhe , sa0 ? 19, la17 ? 23 tristated ? 15 0 ns master write cycles t mmw1 sbhe , sa0 ? 19, la17 ? 23, active to memw (note 1) extime + 45 extime + 65 ns t mmw2 memw active (note 2) mswra ? 10 mswra + 5 ns t mmw3 memw inactive (note 1) extime + 97 extime + 105 ns t mmw4 memw to sbhe , sa0 ? 19, la17 ? 23,sd inactive 45 55 ns t mmw5 sbhe , sa0 ? 19, la17 ? 23, sd hold after memw 45 60 ns t mmw6 sbhe , sa0 ? 19, la17 ? 23, sd setup to memw (note 1) extime + 45 extime + 55 ns t mmw7 iochrdy delay from memw t mmw2 ? 175 ns t mmw8 iochrdy inactive 55 ns t mmw9 iochrdy to memw 130 ns t mmw10 sd active to memw (note 1) extime + 20 extime + 60 ns t mmw11 sd setup to memw (note 1) extime + 20 extime + 60 ns master read cycles t mmr1 sbhe , sa0 ? 19, la17 ? 23, active to memr (note 1) extime + 45 extime + 60 ns t mmr2 memr active (note 2) msrda ? 10 msrda + 5 ns t mmr3 memr inactive (note 1) extime + 97 extime + 105 ns t mmr4 memr to sbhe , sa0 ? 19, la17 ? 23 inactive 45 55 ns t mmr5 sbhe , sa0 ? 19, la17 ? 23 hold after memw 45 55 ns t mmr6 sbhe , sa0 ? 19, la17 ? 23 setup to memr (note 1) extime + 45 extime + 55 ns t mmr7 iochrdy delay from memr t mmr2 ? 175 ns t mmr8 iochrdy inactive 55 ns t mmr9 iochrdy to memr 130 ns t mmr10 sd setup to memr 30 ns t mmr11 sd hold after memr 0ns
am79c961a 139 switching characteristics: bus master mode (continued) notes: 1. extime is 100 ns when isacsr2, bit 4, is cleared (default). extime is 0 ns when isacsr2, bit 4, is set. 2. msrda and mswda are parameters which are defined in registers isacsr0 and isacsr1, respectively. parameter symbol parameter description test conditions min max unit master mode address prom read t ma1 ior to apcs 125 260 ns t ma2 apcs active 140 155 ns t ma3 prdb setup to apcs 20 ns t ma4 prdb hold after apcs 0ns t ma5 apcs to iochrdy 45 65 ns t ma6 sd valid from iochrdy 0 10 ns master mode boot prom read t mb1 ref , sbhe ,sa0 ? 19 setup to smemr 10 ns t mb2 ref , sbhe ,sa0 ? 19 hold smemr 5ns t mb3 iochrdy delay from smemr 035ns t mb4 smemr inactive 55 ns t mb5 smemr to bpcs 125 260 ns t mb6 bpcs active 290 305 ns t mb7 bpcs to iochrdy 45 65 ns t mb8 prdb setup to bpcs 20 ns t mb9 prdb hold after bpcs 0ns t mb10 sd valid from iochrdy 0 10 ns t mb11 sd hold after smemr 020ns t mb12 la20 ? 23 hold from bale 10 ns t mb13 la20 ? 23 setup to memr 10 ns t mb14 bale setup to memr 10 ns
140 am79c961a switching characteristics: bus master mode ? flash read cycle switching characteristics: bus master mode ? flash write cycle parameter symbol parameter description test conditions min max unit t mfr1 ref, sbhe,sa0 ? 19 setup to memr 10 ns t mfr2 ref, sbhe,sa0 ? 19 hold from memr 5ns t mfr3 iochrdy to memr 035ns t mfr4 memr inactive 55 ns t mfr5 memr to bpcs 125 260 ns t mfr6 bpcs active 190 205 ns t mfr7 bpcs to iochrdy 45 65 ns t mfr8 prdb setup to of bpcs 20 ns t mfr9 prdb hold to of bpcs 0ns t mfr10 sd valid from iochrdy 0 10 ns t mfr11 sd tristate to memr 020ns t mfr12 la20 ? 23 hold from bale 10 ns t mfr13 la20 ? 23 setup to memr 10 ns t mfr14 bale setup to memr 15 ns parameter symbol parameter description test conditions min max unit t mfw1 sbhe , sa0 ? 19 setup to memw 10 ns t mfw2 sbhe , sa0 ? 19 hold from memw 5ns t mfw3 iochrdy to memw 035ns t mfw4 memw inactive 50 ns t mfw5 fl_we to iochrdy 20 90 ns t mfw6 memw hold from iochrdy 0ns t mfw7 sd valid from memw 175 ns t mfw8 sd hold from memw 0ns t mfw9 prdb valid from memw 175 ns t mfw10 prdb setup to fl_we 15 ns t mfw11 fl_we active 140 155 ns t mfw12 prdb hold from fl_we 15 t mfw13 la20 ? 23 hold from bale 10 ns t mfw14 la20 ? 23 setup to memw 10 ns t mfw15 bale setup to memw 15 ns
am79c961a 141 switching characteristics: shared memory mode (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) parameter symbol parameter description test conditions min max unit input/output write timing t iow1 aen, sbhe , sa0 ? 9 setup to iow 10 ns t iow2 aen, sbhe ,sa0 ? 9 hold from iow 5ns t iow3 iow assertion 150 ns t iow4 iow inactive 55 ns t iow5 sd setup to iow 10 ns t iow6 sd hold after iow 10 ns t iow7 iochrdy delay from iow 035ns t iow8 iochrdy inactive 125 ns t iow9 iochrdy to iow 0ns input/output read timing t ior1 aen, sbhe , sa0 ? 9 setup to ior 15 ns t ior2 aen, sbhe ,sa0 ? 9 hold after ior 5ns t ior3 ior inactive 55 ns t ior4 sd hold from ior 020ns t ior5 sd valid from ior 0110ns t ior6 iochrdy delay from ior 035ns t ior7 iochrdy inactive 125 ns t ior8 sd valid from iochrdy ? 130 10 ns memory write timing t mw1 sa0 ? 15, sbhe , smam setup to memw 10 ns t mw2 sa0 ? 15, sbhe , smam hold from memw 5ns t mw3 memw assertion 150 ns t mw4 memw inactive 55 ns t mw5 sd setup to memw 10 ns t mw6 sd hold from memw 10 ns t mw7 iochrdy delay from memw 035ns t mw8 iochrdy inactive 125 ns t mw9 memw to iochrdy 0ns
142 am79c961a switching characteristics: shared memory mode (continued) parameter symbol parameter description test conditions min max unit memory read timing t mr1 sa0 ? 15, sbhe , smam /bpam setup to memr 10 ns t mr2 sa0 ? 15, sbhe , smam /bpam hold from memr 5ns t mr3 memr inactive 55 ns t mr4 sd hold from memr 020ns t mr5 sd valid from memr 0110ns t mr6 iochrdy delay from memr 035ns t mr7 iochrdy inactive 125 ns t mr8 sd valid from iochrdy ? 130 10 ns i/o to memory command inactive t iom1 iow /memw to (s )memr /ior 55 ns t iom2 ( s ) memr /ior to iow /memw 55 ns iocs16 timing t iocs1 aen, sbhe , sa0 ? 9 to iocs16 035ns t iocs2 aen, sbhe , sa0 ? 9 to iocs16 tristated 025ns sram read/write, boot prom read, address prom read on private bus t pr4 prab change to prab change, sram access 95 105 ns t pr5 prdb setup to prab change, sram access 20 ns t pr6 prdb hold from prab change, sram access 0ns t pr7 prab change to prab change, aprom access 145 155 ns
am79c961a 143 switching characteristics: shared memory mode (continued) parameter symbol parameter description test conditions min max unit sram read/write, boot prom read, address prom read on private bus (continued) t pr8 prdb setup to prab change, aprom access 20 ns t pr9 prdb hold after prab change, aprom access 0ns t pr10 prab change to prab change, bprom access 290 305 ns t pr11 prdb setup to prab change, bprom access 20 ns t pr12 prdb hold after prab change, bprom access 0ns t pr13 prab change to prab change, sram write 145 155 ns t pr14 prab change to srwe 20 30 ns t pr15 prab change to srwe 120 130 ns t pr16 prab change to prab change, flash access 190 205 ns t pr17 prab change to prab change, flash write 190 205 ns t pr18 prab change to srwe 170 180 ns
144 am79c961a switching characteristics: shared memory mode ? flash read cycle switching characteristics: shared memory mode ? flash write cycle parameter symbol parameter description test conditions min max unit t mfr1 bpam, ref, sbhe, sa0 ? 19 setup to memr 10 ns t mfr2 bpam, ref, sbhe, sa0 ? 19 hold from memr 5ns t mfr3 iochrdy to memr 035ns t mfr4 memr inactive 55 ns t mfr5 memr to bpcs /sroe 125 260 ns t mfr6 bpcs /sroe active 190 205 ns t mfr7 bpcs /sroe to iochrdy 45 65 ns t mfr8 prdb setup to of bpcs /sroe 20 ns t mfr9 prdb hold to of bpcs /sroe 0ns t mfr10 sd valid from iochrdy 0 10 ns t mfr11 sd tristate to memr 020ns parameter symbol parameter description test conditions min max unit t mfw1 bpam, sbhe, sa0 ? 19 setup to memw 10 ns t mfw2 bpam, sbhe, sa0 ? 19 hold after memw 5ns t mfw3 iochrdy to memw 035ns t mfw4 memw inactive 50 ns t mfw5 srwe to iochrdy 20 90 ns t mfw6 memw hold from iochrdy 0ns t mfw7 sd valid from memw 175 ns t mfw8 sd hold from memw 0ns t mfw9 bpcs /prdb valid from memw 175 ns t mfw10 bpcs /prdb setup to srwe 15 ns t mfw11 srwe active 140 155 ns t mfw12 bpcs /prdb hold from srwe 15 ns
am79c961a 145 switching characteristics: eadi (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) note: external address detection interface is invoked by setting bit 3 in isacsr2 and resetting bit 0 in isacsr2. external mau select is not available when eadisel bit is set. switching characteristics: jtag (ieee 1149.1) interface (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) note: jtag logic is reset with an internal power-on reset circuit independent of sleep modes. parameter symbol parameter description test conditions min max unit t ead1 srd setup to srdclk 40 ns t ead2 srd hold to srdclk 40 ns t ead3 sf / bd change to srdclk ? 15 +15 ns t ead4 ear deassertion to srdclk (first rising edge) 50 ns t ead5 ear assertion from sfd event (packet rejection) 051,090ns t ead6 ear assertion 110 ns parameter symbol parameter description test conditions min max unit t jtg1 tck high assertion 20 ns t jtg2 tck period 100 ns t jtg3 tdi setup to tck 5 ns t jtg4 tdi, tms hold from tck 5 ns t jtg5 tms setup to tck 8 ns t jtg6 tdo active from tck 0 30 ns t jtg7 tdo change from tck 0 30 ns t jtg8 tdo tristate from tck 0 25 ns
146 am79c961a switching characteristics: gpsi (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) notes: 1. clsn must be asserted for a continuous period of 110 ns or more. assertion for less than 110 ns period may or may not result in clsn recognition. 2. rclk should meet jitter requirements of ieee 802.3 specification. 3. clsn assertion before 51.2 s will be indicated as a normal collision. clsn assertion after 51.2 s will be considered as a late receive collision. parameter symbol parameter description test conditions min max unit transmit timing t gpt1 stdclk period (802.3 compliant) 99.99 100.01 ns t gpt2 stdclk high time 40 60 ns t gpt3 txdat and txen delay from tclk 0 70 ns t gpt4 rxcrs setup to stdclk (last bit) 210 ns t gpt5 rxcrs hold from tena 0 ns t gpt6 clsn active time to trigger collision (note 1) 110 ns t gpt7 clsn active to rxcrs to prevent lcar assertion 0ns t gpt8 clsn active to rxcrs for sqe hearbeat window 04.0 s t gpt9 clsn active to rxcrs for normal collision 0 51.2 s receive timing t gpr1 srdclk period (note 2) 80 120 ns t gpr2 srdclk high time (note 2) 30 80 ns t gpr3 srdclk low time (note 2) 30 80 ns t gpr4 rxdat and rxcrs setup to srdclk 15 ns t gpr5 rxdat hold from rclk 15 ns t gpr6 rxcrs hold from srdclk 0 ns t gpr7 clsn active to first srdclk (collision recognition) 0ns t gpr8 clsn active to srdclk for address type designation bit (note 3) 51.2 s t gpr9 clsn setup to last srdclk for collision recognition 210 ns t gpr10 clsn active 110 ns t gpr11 clsn inactive setup to first rclk 300 ns t gpr12 clsn inactive hold to last rclk 300 ns
am79c961a 147 switching characteristics: aui (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) notes: 1. di pulses narrower than t pwodi (min) will be rejected; pulses wider than t pwodi (max) will turn internal di carrier sense on. 2. di pulses narrower than t pwkdi (min) will maintain internal di carrier sense on; pulses wider than t pwkdi (max) will turn internal di carrier sense off. 3. ci pulses narrower than t pwoci (min) will be rejected; pulses wider than t pwoci (max) will turn internal ci carrier sense on. 4. ci pulses narrower than t pwkci (min) will maintain internal ci carrier sense on; pulses wider than t pwkci (max) will turn internal ci carrier sense off. parameter symbol parameter description test conditions min max unit aui port t dotr do+,do- rise time (10% to 90%) 2.5 5.0 ns t dotf do+,do- fall time (90% to 10%) 2.5 5.0 ns t dorm do+,do- rise and fall time mismatch 1.0 ns t doetd do+/- end of transmission 200 375 ns t pwodi di pulse width accept/reject threshold |v in | > |v asq | (note 1) 15 45 ns t pwkdi di pulse width maintain/turn-off threshold |v in | > |v asq | (note 2) 136 200 ns t pwoci ci pulse width accept/reject threshold |v in | > |v asq | (note 3) 10 26 ns t pwkci ci pulse width maintain/turn-off threshold |v in | > |v asq | (note 4) 90 160 ns internal mendec clock timing t x1 xtal1 period v in = external clock 49.995 50.005 ns t x1h xtal1 high pulse width v in = external clock 20 ns t x1l xtal1 low pulse width v in = external clock 20 ns t x1r xtal1 rise time v in = external clock 5 ns t x1f xtal1 fall time v in = external clock 5 ns
148 am79c961a switching characteristics: 10base-t interface (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) note: 1. not tested; parameter guaranteed by characterization. switching characteristics: serial eeprom interface (unless otherwise noted, parametric values are the same between commercial devices and industrial devices) parameter symbol parameter description test conditions min max unit transmit timing t tetd transmit start of idle 250 350 ns t tr transmitter rise time (10% to 90%) 5.5 ns t tf transmitter fall time (90% to 10%) 5.5 ns t tm transmitter rise and fall time mismatch 2ns t perlp idle signal period 8 24 ms t pwlp idle link pulse width (note 1) 75 120 ns t pwplp predistortion idle link pulse width (note 1) 45 55 ns t ja transmit jabber activation time 20 150 ms t jr transmit jabber reset time 250 750 ms receive timing t pwnrd rxd pulse width not to turn off internal carrier sense vin > vths (min) 136 ns t pwroff rxd pulse width to turn off vin > vths (min) 200 ns parameter symbol parameter description test conditions min max unit t sr1 eesk high time 790 ns t sr2 eesk low time 790 ns t sr3 eecs eedi from eesk ? 15 15 ns t sr4 eecs, eedi and shfbusy from eesk ? 15 15 ns t sr5 eecs low time 1590 ns t sr6 eedo setup to eesk 35 ns t sr7 eedo hold from eesk 0 ns t sl1 eedo setup to ior 95 ns t sl2 eedo setup to iochrdy 140 ns t sl3 eesk, eedi, eecs and shfbusy delay from iow 160 235 ns
am79c961a 149 switching test circuits ks000010 must be steady may change from h to l may change from l to h does not apply don ? t care, any change permitted will be steady will be changing from h to l will be changing from l to h changing, state unknown center line is high- impedance ? off ? state waveform inputs outputs
150 am79c961a switching test circuits 19364b-32 c l v threshold i ol i oh normal and three-state outputs sense point 19364b-33 av dd do+ 154 ? 100 pf do ? av ss 52.3 ? te s t po i n t aui do switching test circuit
am79c961a 151 switching test circuits txd switching test circuit dv dd txd+ 294 ? 100 pf txd ? dv ss 294 ? te s t po i n t 19364b-34 includes test jig capacitance txd outputs test circuit dv dd txp+ 715 ? 100 pf txp ? dv ss 715 ? te s t po i n t includes test jig capacitance 19364b-35
152 am79c961a switching waveforms: bus master mode i/o write without wait states 19364b-36 aen, sbhe , sa0 ? 9 iow sd t iow5 t iow6 t iow4 t iow1 t iow3 t iow2 stable aen, sbhe , sa0 ? 9 iow sd t iow5 t iow6 t iow4 t iow1 t iow2 stable iochrdy t iow7 t iow8 t iow9 19364b-37 i/o write with wait states
am79c961a 153 switching waveforms: bus master mode serial shift eeprom interface read timing 19364b-38 eesk (prdb0) eecs eedi (prdb1) eedo (prdb2) shfbusy 011 a7 a6 a5 a4 a3 a2 a1 a0 d0 d1 d2 d14 d15 falling transition at 26th word, if checksum is 0xff. 0 19364b-39 serial eeprom control timing eesk (prdb0) eecs eedi (prdb1) shfbsy eed0 (prdb2) t sr1 t sr2 t sr3 t sr4 t sr5 stable t sr6 t sr7
154 am79c961a switching waveforms: bus master mode slave serial eeprom latency timing 19364b-40 t sl1 t sl2 t sl3 eed0 (prdb2) ior iochrdy iow eesk, eedi, eecs, shfbusy 19364b-41 i/o read without wait states aen, sbhe , sa0 ? 9 ior sd t ior5 t ior4 t ior3 t ior1 t ior2 stable stable
am79c961a 155 switching waveforms: bus master mode i/o read with wait states 19364b-42 aen, sbhe , sa0 ? 9 ior sd t ior8 t ior4 t ior3 t ior1 t ior2 stable iochrdy t ior6 t ior7 stable 19364b-43 i/o to memory command inactive time iow , memw memr , ior t iom1 t iom2
156 am79c961a switching waveforms: bus master mode iocs16 timings 19364b-44 aen, sbhe , sa0 ? 9 iocs16 t iocs t iocs2 19364b-45 bus acquisition t mma1 t mma2 t mma3 t mma4 t mma5 ref drq dack master memr /memw sbhe , sa0 ? 19, la17 ? 23
am79c961a 157 switching waveforms: bus master mode bus release 19364b-46 t mmbr1 t mmbr4 drq dack master memr/memw t mmbr2 t mmbr3 sbhe , sa0 ? 19, la17 ? 23 19364b-47 write cycles t mmw1 t mmw2 t mmw3 t mmw4 t mmw7 t mmw8 t mmw9 t mmw5 t mmw6 sbhe , sa0 ? 19, la17 ? 23 memw iochrdy sd0 ? 15 (non wait) (wait states added) t mmw11 t mmw10
158 am79c961a switching waveforms: bus master mode t mmr1 t mmr2 t mmr3 t mmr4 t mmr7 t mmr8 t mmr9 t mmr10 t mmr11 t mmr10 t mmr11 stable stable stable stable t mmr5 t mmr6 sbhe , sa0 ? 19, la17 ? 23 memr iochrdy sd0 ? 15 19364b-48 (non wait) (wait states added) read cycles stable stable t ior1 t ior2 t ior3 t ma5 t ior6 t ma1 t ma2 t ma3 t ma4 t ma6 t ior4 aen, sbhe, sa0 ? 9 ior iochrdy apcs (irq15) prdb0 ? 7 sd0 ? 7 19364b-49 external address prom read cycle
am79c961a 159 switching waveforms: bus master mode stable stable t mb1 t mb2 t mb4 t mb7 t mb3 t mb5 t mb6 t mb8 t mb9 t mb10 t mb11 ref , sbhe , sa0 ? 19 memr iochrdy bpcs prdb0 ? 7 sd0 ? 7 19634b-50 bale stable la20 ? 23 t mb12 t mb13 t mb14 boot prom read cycle
160 am79c961a switching waveforms: bus master mode stable stable t mfr1 t mfr2 t mfr4 t mfr7 t mfr3 t mfr5 t mfr6 t mfr8 t mfr9 t mfr10 t mfr11 ref , sbhe , sa0 ? 19 memr iochrdy bpcs prdb0 ? 7 sd0 ? 7 19364b-51 bale stable la20 ? 23 t mfr12 t mfr13 t mfr14 flash read cycle
am79c961a 161 switching waveforms: bus master mode t mfw5 stable t mfw1 t mfw2 t mfr4 t mfw3 t mfw7 sbhe , sa0 ? 19 memw iochrdy sd0-7 bale stable la20 ? 23 t mfw13 t mfw14 t mfw15 t mfw6 t mfw8 fl_we (irq12) t mfw11 t mfw10 t mfw12 stable stable prdb0-7 19364b-52 t mfw9 flash write cycle
162 am79c961a switching waveforms: shared memory mode stable aen, sbhe , sa0 ? 9 iow sd t iow6 t iow5 19364b-53 t iow t iow1 t iow t iow4 i/o write without wait states stable aen, sbhe , sa0 ? 9 iow sd t iow t iow5 19664b-54 iochrdy t iow1 t iow2 t iow t iow8 t iow9 t iow4 i/o write with wait states
am79c961a 163 switching waveforms: shared memory mode t ior1 stable aen, sbhe, sa0 ? 9 ior sd t ior4 t ior5 stable t ior2 t ior3 19364b-55 i/o write without wait states stable aen, sbhe , sa0 ? 9 ior t ior2 iochrdy sd t ior4 stabl t ior3 t ior6 t ior7 t ior1 t ior8 19364b-56 i/o read with wait states
164 am79c961a switching waveforms: shared memory mode stable sa0 ? 15, sbhe smam sd t mw2 t mw6 t mw5 memw t mw4 t mw1 t mw3 19364b-57 memory write without wait states stable sa0 ? 15, sbhe smam sd t mw4 t mw6 t mw5 memw t mw7 t mw8 t mw9 iochrdy t mw2 t mw1 19364b-58 memory write with wait states
am79c961a 165 switching waveforms: shared memory mode stable stable t mr1 t mr2 t mr5 t mr4 t mr3 sa0 ? 15, sbhe smam memr sd 19364b-59 memory read without wait states stable stable t mr1 t mr2 t mr6 t mr3 sa0 ? 15, sbhe smam /bpam memr sd t mr7 t mr8 t mr4 iochrdy 19364b-60 memory write with wait states
166 am79c961a switching waveforms: shared memory mode t iom2 iow , memw memr , ior t iom1 i/o to memory command inactive time 19364b-61 aen, sbhe, sa0 ? 9 iocs16 t iocs1 t iocs2 iocs16 timings 19364b-62
am79c961a 167 switching waveforms: shared memory mode t sfw5 stable t sfw1 t sfw2 t sfr4 t sfw3 t sfw7 sbhe, sa0 ? 15, bpam memw iochrdy sd0-7 t sfw6 t sfw8 srwe t sfw11 t sfw10 t sfw12 stable stable prdb0-7 t sfw9 bpcs flash write cycle 19364b-63
168 am79c961a switching waveforms: shared memory mode t sfr7 stable t sfr1 t sfr2 t sfr4 t sfr3 ref, sbhe sa0-15 memr iochrdy sroe bpcs stable t sfr8 t sfr9 t sfr10 t sfr11 prdb0 ? 7 sd0 ? 7 t sfr5 t sfr6 flash read cycle 19364b-64
am79c961a 169 switching waveforms: shared memory mode t pr13 t pr13 t pr15 t pr15 t pr14 t pr14 prab srwe prdb srcs (irq12) sram write on private bus (when fl_sel is enabled) 19364b-65 t pr4 t pr4 prab sroe prdb t pr6 t pr5 t pr6 t pr5 srcs (irq12) sram read on private bus (when fl_sel is enabled) 19364b-66
170 am79c961a switching waveforms: shared memory mode t pr10 t pr10 prab bpcs prdb t pr12 t pr11 t pr12 t pr11 boot prom read on private bus 19364b-67 prab0 ? 9 apcs (irq15) prdb t pr9 address prom read on private bus 19364b-68 t pr8 t pr7
am79c961a 171 switching waveforms: shared memory mode t pr17 t pr17 t pr14 t pr14 t pr18 t pr18 prab0 srwe prdb flcs flash write on private bus 19364b-69 t pr16 t pr16 prab0 prdb floe flcs t pr12 t pr11 t pr12 t pr11 19364b-70 flash read on private bus
172 am79c961a switching waveforms: gpsi notes: 1. rxcrs is not present during transmission, lcar bit in tmd3 will be set. 2. clsn is not present during or shortly after transmission, cerr in csr0 will be set. tr a n s m i t clock ( stdclk) transmit data (txdat) tr a n s m i t enable (txen) carrier present (rxcrs) (note 1) collision (clsn) (note 2) (first bit preamble) t gpt2 t gpt3 t gpt3 t gpt3 t gpt5 (last bit) 19364b-71 transmit timing t gpt1 t gpt9 t gpt6 t gpt7 t gpt8 t gpt4 receive clock (srdclk) (first bit preamble) (address type designation bit) (last bit) t gpr2 t gpr3 t gpr4 t gpr5 t gpr5 t gpr6 t gpr8 t gpr9 t gpr11 t gpr12 receive data (rxdat) carrier present (rxcrs) collision (clsn), active collision (clsn), inactive t gpr4 receive timing 19364b-72 t gpr1 t gpr7 t gpr10 (no collision)
am79c961a 173 switching waveforms: eadi switching waveforms: jtag (ieee 1149.1) interface ear (mausel) srdclk (led3) srd (led2) sf/bd (led1) t ead4 t ead1 t ead2 one zero one sfd bit 0 bit 1 bit 2 bit 3 bit 4 bit 8 bit 0 bit 7 bit 8 t ead3 t ead3 t ead5 t ead6 preamble data field reject accept eadi reject timing 19364b-73 tck t jtg3 t jtg4 t jtg2 t jtg5 tdi tms tdo t jtg6 t jtg7 t jtg8 test access port timing t jtg1 19364b-74
174 am79c961a switching waveforms: aui note: 1. internal signal and is shown for clarification only. t xi t dotr t dotf t x1h t x1l t x1f t x1r 1 1 0 1 xtal1 istdclk (note 1) itxdat+ (note 1) do+ do ? do 0 1 1 itxen (note 1) 19364b-75 transmit timing ? start of packet
am79c961a 175 switching waveforms: aui note: 1. internal signal and is shown for clarification only. typical > 200 ns t doetd xtal1 istdclk (note 1) itxen (note 1) itxdat+ (note 1) do+ do ? do 0 1 0 0 10 bit (n ? 2) bit (n ? 1) bit (n) 1 19364b-76 transmit timing ? end of packet (last bit = 0)
176 am79c961a switching waveforms: aui note: 1. internal signal and is shown for clarification only. typical > 250 ns xtal1 itxen (note 1) itxdat+ (note 1) do+ do ? do 0 11 0 1 bit (n ? 2) bit (n ? 1) bit (n) 1 istdclk (note 1) transmit timing ? end of packet (last bit = 1) t doetd 19364b-77
am79c961a 177 switching waveforms: aui di+/ ? v asq t pwodi t pwkdi t pwkdi receive timing diagram 19364b-78 ci+/ ? v asq t pwoci t pwkci t pwkci collision timing diagram 19364b-79 t doetd do+/ ? 40 mv 100 mv max. 0 v port do etd waveform 19364b-80 80 bit times
178 am79c961a switching waveforms: 10base-t interface note: 1. internal signal and is shown for clarification only. t tr t tf t tetd txd+ txp+ txd ? txp ? xmt (note 1) transmit timing 19364b-81 txd+ t perlp t pwlp t pwplp txp+ txd ? txp ? idle link test pulse 19364b-82
am79c961a 179 switching waveforms: 10base-t interface rxd v tsq+ v tsq ? v ths ? v ths+ receive thresholds (lrt = 0 in csr15 bit 9) 19364b-83 rxd v lt s q+ v lt s q ? v lt h s ? v lt h s + receive thresholds (lrt = 1 in csr15 bit 9) 19364b-84
180 am79c961a physical dimensions* pqb132 plastic quad flat pack trimmed and formed (measured in inches) pin 132 pin 99 pin 66 pin 1 i.d. 16-038-pqb pqb132 db87 7-26-94 ae top view 1.097 1.103 0.947 0.953 1.075 1.085 1.097 1.103 0.008 0.012 pin 33 1.075 1.085 0.947 0.953 0.025 basic 0.160 0.180 0.80 ref bottom view 0.130 0.150 0.020 0.040 seating plane pin 132 pin 99 pin 66 pin 1 i.d. top view 1.097 1.103 0.947 0.953 1.075 1.085 1.097 1.103 0.008 0.012 pin 33 1.075 1.085 0.947 0.953 0.025 basic 0.160 0.180 0.80 ref bottom view 0.130 0.150 0.020 0.040 seating plane
am79c961a 181 physical dimensions* pqb132 molded carrier ring plastic quad flat pack (measured in inches, ring measured in millimeters) 45.87 46.13 45.50 45.90 41.37 41.63 37.87 38.13 35.15 35.25 32.15 32.25 1.097 1.103 .944 .952 .944 .952 1.097 1.103 32.15 32.25 35.15 35.25 37.87 38.13 41.37 41.63 45.50 45.90 45.87 46.13 .750 nom. pin 132 pin 1 4.80 2.00 256 nom. side view 1.50 dia. 1.80 pin 99 pin 66 z1 1.50 dia. pin 33 z2 1.50 dia.
182 am79c961a
appendix a am79c961a 183 pcnet-isa ii compatible media interface modules pcnet-isa ii compatible 10base-t filters and transformers the table below provides a sample list of pcnet-isa ii compatible 10base-t filter and transformer modules available from various vendors. contact the respective manufacturer for a complete and updated listing of components. pcnet-isa ii compatible aui isolation transformers the table below provides a sample list of pcnet-isa ii compatible aui isolation transformers available from various vendors. contact the respective manufacturer for a complete and updated listing of components. manufacturer part no. package filters and transformers filters transformers and choke filters transformers dual choke filters transformers dual chokes bel fuse a556-2006-de 16-pin 0.3" dil bel fuse 0556-2006-00 14-pin sip bel fuse 0556-2006-01 14-pin sip bel fuse 0556-6392-00 16-pin 0.5" dil halo electronics fd02-101g 16-pin 0.3" dil halo electronics fd12-101g 16-pin 0.3" dil halo electronics fd22-101g 16-pin 0.3" dil pca electronics epa1990a 16-pin 0.3" dil pca electronics epa2013d 16-pin 0.3" dil pca electronics epa2162 16-pin 0.3" sip pulse engineering pe-65421 16-pin 0.3" dil pulse engineering pe-65434 16-pin 0.3" sil pulse engineering pe-65445 16-pin 0.3" dil pulse engineering pe-65467 12-pin 0.5" smt valor electronics pt3877 16-pin 0.3" dil valor electronics fl1043 16-pin 0.3" dil manufacturer part no. package description bel fuse a553-0506-ab 16-pin 0.3" dil 50 h bel fuse s553-0756-ae 16-pin 0.3" smd 75 h halo electronics td01-0756k 16-pin 0.3" dil 75 h halo electronics tg01-0756w 16-pin 0.3" smd 75 h pca electronics ep9531-4 16-pin 0.3" dil 50 h pulse engineering pe64106 16-pin 0.3" dil 50 h pulse engineering pe65723 16-pin 0.3" smt 75 h valor electronics lt6032 16-pin 0.3" dil 75 h valor electronics st7032 16-pin 0.3" smd 75 h
184 am79c961a pcnet-isa ii compatible dc/dc converters the table below provides a sample list of pcnet-isa ii compatible dc/dc converters available from various vendors. contact the respective manufacturer for a complete and updated listing of components. manufacturer contact information contact the following companies for further information on their products: manufacturer part no. package voltage remote on/off halo electronics dcu0-0509d 24-pin dip 5/-9 no halo electronics dcu0-0509e 24-pin dip 5/-9 yes pca electronics epc1007p 24-pin dip 5/-9 no pca electronics epc1054p 24-pin dip 5/-9 yes pca electronics epc1078 24-pin dip 5/-9 yes valor electronics pm7202 24-pin dip 5/-9 no valor electronics pm7222 24-pin dip 5/-9 yes company u.s. and domestic asia europe bel fuse phone: fax: (201) 432-0463 (201) 432-9542 852-328-5515 852-352-3706 33-1-69410402 33-1-69413320 halo electronics phone: fax: (415) 969-7313 (415) 367-7158 65-285-1566 65-284-9466 pca electronics (hpc in hong kong) phone: fax: 818-892-0761 818-894-5791 852-553-0165 852-873-1550 33-1-44894800 33-1-42051579 pulse engineering phone: fax: (619) 674-8100 (619) 675-8262 852-425-1651 852-480-5974 353-093-24107 353-093-24459 valor electronics phone: fax: (619) 537-2500 (619) 537-2525 852-513-8210 852-513-8214 49-89-6923122 49-89-6926542
appendix b am79c961a 185 layout recommendations for reducing noise decoupling low-pass r/c filter design the pcnet-isa ii controller is an integrated, single-chip ethernet controller, which contains both digital and analog circuitry. the analog circuitry contains a high speed phase-locked loop (pll) and voltage con- trolled oscillator (vco). because of the mixed signal characteristics of this chip, some extra precautions must be taken into account when designing with this device. described in this section is a simple decoupling low-pass r/c filter that can significantly increase noise immunity of the pll circuit, thus, prevent noise from disrupting the vco. bit error rate, a common measure- ment of network performance, as a result can be dras- tically reduced. in certain cases the bit error rate can be reduced by orders of magnitude. implementation of this filter is not necessary to achieve a functional product that meets the ieee 802.3 specifi- cation and provides adequate performance. however, this filter will help designers meet those specifications with more margin. digital decoupling the dvss pins that are sinking the most current are those that provide the ground for the isa bus output signals since these outputs require 24 ma drivers. the dvss10 and dvss12 pins provide the ground for the internal digital logic. in addition, dvss11 provides ground for the internal digital and for the input and i/o pins. the cmos technology used in fabricating the pc- net-isa ii controller employs an n-type substrate. in this technology, all v dd pins are electrically connected to each other internally. hence, in a four-layer board, when decoupling between v dd and critical v ss pins, the spe- cific v dd pin that you connect to is not critical. in fact, the v dd connection of the decoupling capacitor can be made directly to the power plane, near the closest v dd pin to the v ss pin of interest. however, we recommend that the v ss connection of the decoupling capacitor be made directly to the v ss pin of interest as shown. amd recommends that at least one low-frequency bulk decoupling capacitor be used in the area of the pcnet-isa ii controller. 22 f capacitors have worked well for this. in addition, a total of four or five 0.1 f capacitors have proven sufficient around the dv ss and dv dd pins that supply the drivers of the isa bus output pins. analog decoupling the most critical pins are the analog supply and ground pins. all of the analog supply and ground pins are located in one corner of the device. specific requirements of the analog supply pins are listed below. avss1 and avdd3 these pins provide the power and ground for the twisted pair and aui drivers. hence, they are very noisy. a dedicated 0.1 f capacitor between these pins is recommended. avss2 and avdd2 these pins are the most critical pins on the pcnet-isa ii controller because they provide the power and ground for the pll portion of the chip. the vco portion of the pll is sensitive to noise in the 60 khz-200 khz range. to prevent noise in this frequency range from disrupting the vco, amd strongly recommends that the low-pass filter shown below be implemented on these pins. tests using this filter have shown signifi- cantly increased noise immunity and reduced bit error rate (ber) statistics in designs using the pcnet-isa ii controller. v dd pin v ss pin pcnet-isa ii via to v dd via to v ss plane 19364b-85
186 am79c961a to determine the value for the resistor and capacitor, the formula is: r * c 88 where r is in ohms and c is in microfarads. some pos- sible combinations are given below. to minimize the voltage drop across the resistor, the r value should not be more than 20 ? . avss2 and avdd2/avdd4 these pins provide power and ground for the aui and twisted pair receive circuitry. no specific decoupling has been necessary on these pins. pcnet-isa ii av dd2 pin 108 av ss2 pin 98 v dd plane 33 f to 6.8 f r1 1 ? to 20 ? 19364b-86 rc 2.7 ? 33 f 4.3 ? 22 f 6.8 ? 15 f 10 ? 10 f 20 ? 6.8 f
appendix c 187 sample plug and play configuration record sample configuration file the following is a sample configuration record for the pcnet-isa ii device used in an amd ethernet card. this card requires one dma channel, one interrupt, one i/o port in the 0x200-0x3ff range (0x20 bytes aligned). the vendor id of amd is adv. the vendor assigned part number for this card is 2100 and the se- rial number is 0x12345678. the card has only one log- ical device, that is an ethernet controller. there are no compatible devices with this logical device. the follow- ing record should be returned by the card during the identification process. note: all data stored in the eeprom is stored in bit-reversal for- mat. each word (16 bits) must be written into the eeprom with bit 15 swapped with bit 0, bit 14 swapped with bit 1, etc. ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; plug and play header ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; db 0x04 ; vendor eisa id byte 0 db 0x96 ; vendor eisa id byte 1 db 0x00 ; vendor assigned id byte 0 db 0x21 ; vendor assigned id byte 1 db 0x78 ; serial number byte 0 db 0x56 ; serial number byte 1 db 0x34 ; serial number byte 2 db 0x12 ; serial number byte 3 db checksum ; checksum calculated on above bits ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; plug and play version ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; db 0x0a ; small item, plug and play version db 0x10 ; bcd major version [7:4] = 1 ; bcd minor version [3:0] = 0 db 0x00 ; vendor specific version number ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; identifier string ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; db 0x82 ; large item, type identifier string (ansi) db 0x1c ; length byte 0 (28 bytes) db 0x00 ; length byte 1 db ?amd pcnet-isa ii ethernet network adapter? ; identifier string
188 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; logical device id ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x15 ; small item, type logical device id db 0x04 ; logical device id byte 0 db 0x96 ; logical device id byte 1 db 0x55 ; logical device id byte 2 db 0xaa ; logical device id byte 3 db 0x02 ; logical device flags [0] ? required for boot ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; compatible device id ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x1c ; small item, type compatible device id db 0x41 ; compatible device id byte 0 db 0xd0 ; compatible device id byte 1 db 0x82 ; compatible device id byte 2 db 0x8c ; compatible device id byte 3 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; i/o port descriptor ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x47 ; small item, type i/o port db 0x00 ; information, [0] = 0, 10 bit decode db 0x00 ; minimum base address [07:00] db 0x02 ; minimum base address [15:08] db 0xe0 ; maximum base address [07:00] db 0x03 ; maximum base address [15:08] db 0x20 ; base address increment (32 ports) db 0x18 ; number of ports required ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; dma descriptor ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x2a ; small item, type dma format db 0xe8 ; dma channel mask ch 3, 5, 6, 7 db 0x05 ; 16-bit only, bus master ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;irq format ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x23 ; small item, type irq format db 0x38 ; irqs supported [7:0] 3, 4, 5 db 0x9e ; irqs supported [15:8] 9, 10, 11, 12, 15 db 0x09 ; information: high true, edge low true, level ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; end tag ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; db 0x79 ; small item, type end tag db checksum ; checksum
appendix d am79c961a 189 alternative method for initialization the pcnet-isa ii controller may be initialized by performing i/o writes only. that is, data can be written directly to the appropriate control and status registers (csr) instead of reading from the initialization block in memory. the registers that must be written are shown in the table below. these are followed by writing the start bit in csr0. note: the init bit must not be set or the initialization block will be accessed instead. control and status register comment csr8 ladrf[15:0] csr9 ladrf[31:16] csr10 ladrf[47:32] csr11 ladrf[63:48] csr12 padr[15:0] csr13 padr[31:16] csr14 padr[47:32] csr15 mode csr24 ? 25 badr csr30 ? 31 badx csr47 pollint csr76 rcvrl csr78 xmtrl
190 am79c961a
appendix e am79c961a 191 introduction of the look- ahead packet processing (lapp) concept a driver for the pcnet-isa ii controller would normally require that the cpu copy receive frame data from the controller ? s buffer space to the application ? s buffer space after the entire frame has been received by the controller. for applications that use a ping-pong windowing style, the traffic on the network will be halted until the current frame has been completely processed by the entire application stack. this means that the time between last byte of a receive frame arriving at the client ? s ethernet controller and the client ? s transmission of the first byte of the next outgoing frame will be separated by: 1. the time that it takes the client ? s cpu ? s interrupt procedure to pass software control from the current task to the driver 2. plus the time that it takes the client driver to pass the header data to the application and request an application buffer 3. plus the time that it takes the application to generate the buffer pointer and then return the buffer pointer to the driver 4. plus the time that it takes the client driver to transfer all of the frame data from the controller ? s buffer space into the application ? s buffer space and then call the application again to process the complete frame 5. plus the time that it takes the application to process the frame and generate the next outgoing frame 6. plus the time that it takes the client driver to set up the descriptor for the controller and then write a tdmd bit to csr0 the sum of these times can often be about the same as the time taken to actually transmit the frames on the wire, thereby yielding a network utilization rate of less than 50%. an important thing to note is that the pcnet-isa ii con- troller ? s data transfers to its buffer space are such that the system bus is needed by the pcnet-isa ii controller for approximately 4% of the time. this leaves 96% of the system bus bandwidth for the cpu to perform some of the inter-frame operations in advance of the completion of network receive activity , if possible. the question then becomes: how much of the tasks that need to be per- formed between reception of a frame and transmission of the next frame can be performed before the reception of the frame actually ends at the network, and how can the cpu be instructed to perform these tasks during the network reception time? the answer depends upon exactly what is happening in the driver and application code, but the steps that can be performed at the same time as the receive data are arriving include as much as the first three steps and part of the fourth step shown in the sequence above. by performing these steps before the entire frame has arrived, the frame throughput can be substantially increased. a good increase in performance can be expected when the first three steps are performed before the end of the network receive operation. a much more significant performance increase could be realized if the pcnet-isa ii controller could place the frame data directly into the application ? s buffer space; (i.e. eliminate the need for step four). in order to make this work, it is necessary that the application buffer pointer be determined before the frame has com- pletely arrived, then the buffer pointer in the next desriptor for the receive frame would need to be modified in order to direct the pcnet-isa ii controller to write directly to the application buffer. more details on this operation will be given later. an alternative modification to the existing system can gain a smaller, but still significant improvement in per- formance. this alternative leaves step four unchanged in that the cpu is still required to perform the copy operation, but it allows a large portion of the copy oper- ation to be done before the frame has been completely received by the controller, (i.e. the cpu can perform the copy operation of the receive data from the pc- net-isa ii controller ? s buffer space into the application buffer space before the frame data has completely ar- rived from the network). this allows the copy operation of step four to be performed concurrently with the ar- rival of network data, rather than sequentially, following the end of network receive activity. outline of the lapp flow: this section gives a suggested outline for a driver that utilizes the lapp feature of the pcnet-isa ii controller.
192 am79c961a note: the labels in the following text are used as references in the timeline diagram that follows. setup: the driver should set up descriptors in groups of 3, with the own and stp bits of each set of three descriptors to read as follows: 11b, 10b, 00b. an option bit (lappen) exists in csr3, bit position 5. the software should set this bit. when set, the lappen bit directs the pcnet-isa ii to generate an interrupt when stp has been written to a receive descriptor by the pcnet-isa ii controller. flow: the pcnet-isa ii controller polls the current receive descriptor at some point in time before a message arrives. the pcnet-isa ii controller determines that this receive buffer is owned by the pcnet-isa ii controller and it stores the descriptor information to be used when a message does arrive. n0: frame preamble appears on the wire, followed by sfd and destination address. n1: the 64th byte of frame data arrives from the wire. this causes the pcnet-isa ii controller to begin frame data dma operations to the first buffer. c0: when the 64th byte of the message arrives, the pcnet-isa ii controller performs a lookahead oper- ation to the next receive descriptor. this descriptor should be owned by the pcnet-isa ii controller. c1: the pcnet-isa ii controller intermittently requests the bus to transfer frame data to the first buffer as it arrives on the wire. s0: the driver remains idle. c2: when the pcnet-isa ii controller has completely filled the first buffer, it writes status to the first descriptor. c3: when the first descriptor for the frame has been written, changing ownership from the pcnet-isa ii controller to the cpu, the pcnet-isa ii controller will generate an srp interrupt. (this inter- rupt appears as a rint interrupt in csr0.) s1: the srp interrupt causes the cpu to switch tasks to allow the pcnet-isa ii controller ? s driver to run. c4: during the cpu interrupt-generated task switch- ing, the pcnet-isa ii controller is performing a lookahead operation to the third descriptor. at this point in time, the third descriptor is owned by the cpu. [ note: even though the third buffer is not owned by the pcnet-isa ii controller, existing amd ethernet controllers will continue to perform data dma into the buffer space that the controller already owns (i.e. buffer number 2). the controller does not know if buffer space in buffer number 2 will be sufficient or not, for this frame, but it has no way to tell except by trying to move the entire mes- sage into that space. only when the message does not fit will it signal a buffer error condition ? there is no need to panic at the point that it discov- ers that it does not yet own descriptor number 3.] s2: the first task of the driver ? s interrupt service routine is to collect the header information from the pcnet-isa ii controller ? s first buffer and pass it to the application. s3: the application will return an application buffer pointer to the driver. the driver will add an offset to the application data buffer pointer, since the pcnet-isa ii controller will be placing the first portion of the message into the first and second buffers. (the modified application data buffer pointer will only be directly used by the pcnet-isa ii controller when it reaches the third buffer.) the driver will place the modified data buffer pointer into the final descriptor of the group (#3) and will grant ownership of this descriptor to the pc- net-isa ii controller. c5: interleaved with s2, s3 and s4 driver activity, the pcnet-isa ii controller will write frame data to buffer number 2. s4: the driver will next proceed to copy the contents of the pcnet-isa ii controller ? s first buffer to the beginning of the application space. this copy will be to the exact (unmodified) buffer pointer that was passed by the application. s5: after copying all of the data from the first buffer into the beginning of the application data buffer, the driver will begin to poll the ownership bit of the second descriptor. the driver is waiting for the pcnet-isa ii controller to finish filling the second buffer. c6: at this point, knowing that it had not previously owned the third descriptor, and knowing that the current message has not ended (there is more data in the fifo), the pcnet-isa ii controller will make a ? last ditch lookahead ? to the final (third) descriptor; this time, the ownership will be true (i.e. the descriptor belongs to the controller), because the driver wrote the application pointer into this descriptor and then changed the owner- ship to give the descriptor to the pcnet-isa ii con- troller back at s3. note that if steps s1, s2 and s3 have not completed at this time, a buff error will result. c7: after filling the second buffer and performing the last chance lookahead to the next descriptor, the pcnet-isa ii controller will write the status and change the ownership bit of descriptor number 2.
am79c961a 193 s6: after the ownership of descriptor number 2 has been changed by the pcnet-isa ii controller, the next driver poll of the 2nd descriptor will show ownership granted to the cpu. the driver now copies the data from buffer number 2 into the ? middle section ? of the application buffer space. this operation is interleaved with the c7 and c8 operations. c8: the pcnet-isa ii controller will perform data dma to the last buffer, whose pointer is pointing to application space. data entering the last buffer will not need the infamous ? double copy ? that is required by existing drivers, since it is being placed directly into the application buffer space. n2: the message on the wire ends. s7: when the driver completes the copy of buffer number 2 data to the application buffer space, it begins polling descriptor number 3. c9: when the pcnet-isa ii controller has finished all data dma operations, it writes status and changes ownership of descriptor number 3. s8: the driver sees that the ownership of descriptor number 3 has changed, and it calls the application to tell the application that a frame has arrived. s9: the application processes the received frame and generates the next tx frame, placing it into a tx buffer. s10: the driver sets up the tx descriptor for the pc- net-isa ii controller. 19364b-87 figure 1. look ahead packet processing (lapp) timeline buffer #3 buffer #2 buffer #1 ethernet wire activity: ethernet controller activity: software activity: s10: driver sets up tx descriptor. s9: application processes packet, generates tx packet. s8: driver calls application to tell application that packethas arrived. s7: driver polls descriptor of buffer #3. s6: driver copies data from buffer #2 to the application buffer. s5: driver polls descriptor #2. s4: driver copies data from buffer #1 to the application buffer. s3: driver writes modified application pointer to descriptor #3. s2: driver call to application to get application buffer pointer. s1: interrupt latency. s0: driver is idle. } n2:eom n0: packet preamble, sfd and destination address are arriving. { packet data arriving } } } c9: controller writes descriptor #3. c8: controller is performing intermittent bursts of dma to fill data buffer #3. c7: controller writes descriptor #2. c6: "last chance" lookahead to descriptor #3 (own). c5: controller is performing intermittent bursts of dma to fill data buffer #2 c3: srp interrupt is generated. c2: controller writes descriptor #1. c1: controller is performing intermittent bursts of dma to fill data buffer #1. c0: lookahead to descriptor #2. n1: 64th byte of packet data arrives. c4: lookahead to descriptor #3 (own).
194 am79c961a lapp enable software requirements software needs to set up a receive ring with descriptors formed into groups of 3. the first descriptor of each group should have own = 1 and stp = 1, the second descriptor of each group should have own = 1 and stp = 0. the third descriptor of each group should have own = 0 and stp = 0. the size of the first buffer (as indicated in the first descriptor), should be at least equal to the largest expected header size; however, for maximum efficiency of cpu utilization, the first buffer size should be larger than the header size. it should be equal to the expected number of message bytes, minus the time needed for interrupt latency and minus the application call latency, minus the time needed for the driver to write to the third descriptor, minus the time needed for the driver to copy data from buffer #1 to the application buffer space, and minus the time needed for the driver to copy data from buffer #2 to the application buffer space. note that the time needed for the copies performed by the driver depends upon the sizes of the 2nd and 3rd buffers, and that the sizes of the second and third buffers need to be set ac- cording to the time needed for the data copy opera- tions! this means that an iterative self-adjusting mechanism needs to be placed into the software to de- termine the correct buffer sizing for optimal operation. fixed values for buffer sizes may be used; in such a case, the lapp method will still provide a significant performance increase, but the performance increase will not be maximized. the following diagram illustrates this setup for a re- ceive ring size of 9: lapp enable rules for parsing of descriptors when using the lapp method, software must use a modified form of descriptor parsing as follows: software will examine own and stp to determine where a rcv frame begins. rcv frames will only begin in buffers that have own = 0 and stp = 1. software shall assume that a frame continues until it finds either enp = 1 or err= 1. software must discard all descriptors with own = 0 and stp = 0 and move to the next descriptor when searching for the beginning of a new frame; enp and err should be ignored by software during this search. software cannot change an stp value in the receive descriptor ring after the initial setup of the ring is complete, even if software has ownership of the stp descriptor unless the previous stp descriptor in the ring is also owned by the software. when lappen = 1, then hardware will use a modified form of descriptor parsing as follows: the controller will examine own and stp to deter- mine where to begin placing a rcv frame. a new rcv frame will only begin in a buffer that has own = 1 and stp = 1. the controller will always obey the own bit for deter- mining whether or not it may use the next buffer for a chain. the controller will always mark the end of a frame with either enp = 1 or err= 1. descriptor #1 descriptor #2 descriptor #3 descriptor #4 descriptor #5 descriptor #6 descriptor #7 descriptor #8 descriptor #9 own = 1 stp = 1 size = a-(s1+s2+s3+s4+s6) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = s6 own = 1 stp = 1 size = a-(s1+s2+s3+s4+s6) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = s6 own = 1 stp = 1 size = a-(s1+s2+s3+s4+s6) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = s6 a = expected message size in bytes s1 = interrupt latency s2 = application call latency s3 = time needed for driver to write to third descriptor s4 = time needed for driver to copy data from buffer #1 to application buffer space s6 = time needed for driver to copy data from buffer #2 to application buffer space note that the times needed for tasks s1, s2, s3, s4, and s6 should be divided by 0.8 microseconds to yield an equivalent number of network byte times before subtracting these quantities from the expected message size a. 19364b-88 figure 2. lapp 3 buffer grouping
am79c961a 195 the controller will discard all descriptors with own = 1 and stp = 0 and move to the next descriptor when searching for a place to begin a new frame . it dis- cards these desciptors by simply changing the owner- ship bit from own=1 to own = 0. such a descriptor is unused for receive purposes by the controller, and the driver must recognize this. (the driver will recognize this if it follows the software rules.) the controller will ignore all descriptors with own = 0 and stp = 0 and move to the next descriptor when searching for a place to begin a new frame . in other words, the controller is allowed to skip entries in the ring that it does not own, but only when it is looking for a place to begin a new frame. some examples of lapp descriptor interaction choose an expected frame size of 1060 bytes. choose buffer sizes of 800, 200 and 200 bytes. 1. assume that a 1060 byte frame arrives correctly, and that the timing of the early interrupt and the soft- ware is smooth. the descriptors will have changed from: *enp or err 2. assume that instead of the expected 1060 byte frame, a 900 byte frame arrives, either because there was an error in the network, or because this is the last frame in a file transmission sequence. *enp or err ** note that the pcnet-isa ii controller might write a zero to enp location in the 3rd descriptor. here are the two possibilit ies: 1. if the controller finishes the data transfers into buffer number 2 after the driver writes the application ? s modified buffer pointer into the third descriptor, then the controller will write a zero to enp for this buffer and will write a zero to own and stp. 2. if the controller finishes the data transfers into buffer number 2 before the driver writes the application ? s modified buffer pointer into the third descriptor, then the controller will complete the frame in buffer number two and then skip the then unowned thir d buffer. in this case, the pcnet-isa ii controller will not have had the opportunity to reset the enp bit in this descriptor, a nd it is possible that the software left this bit as enp=1 from the last time through the ring. therefore, the software must treat the location as a don ? t care; the rule is, after finding enp=1 (or err=1) in descriptor number 2, the software must ignore enp bits until it finds the next stp=1. descriptor number before the frame arrived after the frame has arrived comments (after frame arrival) own stp enp* own stp enp* 111x010bytes 1 ? 800 2 1 0 x 0 0 0 bytes 801 ? 1000 3 0 0 x 0 0 1 bytes 1001 ? 1060 4 1 1 x 1 1 x controller ? s current location 5 1 0 x 1 0 x not yet used 6 0 0 x 0 0 x not yet used etc. 1 1 x 1 1 x not yet used descriptor number before the frame arrived after the frame has arrived comments (after frame arrival) own stp enp* own stp enp* 111x010bytes 1 ? 800 2 1 0 x 0 0 1 bytes 801 ? 900 3 0 0 x 0 0 ?** discarded buffer 4 1 1 x 1 1 x controller ? s current location 5 1 0 x 1 0 x not yet used 6 0 0 x 0 0 x not yet used etc. 1 1 x 1 1 x not yet used
196 am79c961a 3. assume that instead of the expected 1060 byte frame, a 100 byte frame arrives, because there was an error in the network, or because this is the last frame in a file transmission sequence, or perhaps because it is an acknowledge frame. *enp or err ** same as note in case 2 above, except that in this case, it is very unlikely that the driver can respond to the interrupt and get the pointer from the application before the pcnet-isa ii controller has completed its poll of the next descriptors. this means that for almost all occurrences of this case, the pcnet-isa ii controller will not find the own bit set for this descriptor and therefor e, the enp bit will almost always contain the old value, since the pcnet-isa ii controller will not have had an opportunity to modify it. *** note that even though the pcnet-isa ii controller will write a zero to this enp location, the software should treat the loca tion as a don ? t care, since after finding the enp=1 in descriptor number 2, the software should ignore enp bits until it finds the next stp=1. buffer size tuning for maximum performance, buffer sizes should be adjusted depending upon the expected frame size and the values of the interrupt latency and application call latency. the best driver code will minimize the cpu utilization while also minimizing the latency from frame end on the network to frame sent to application from driver (frame latency). these objectives are aimed at increasing throughput on the network while decreasing cpu utilization. note that the buffer sizes in the ring may be altered at any time that the cpu has ownership of the corre- sponding descriptor. the best choice for buffer sizes will maximize the time that the driver is swapped out, while minimizing the time from the last byte written by the pcnet-isa ii controller to the time that the data is passed from the driver to the application. in the diagram, this corresponds to maximizing s0, while min- imizing the time between c9 and s8. (the timeline happens to show a minimal time from c9 to s8.) note that by increasing the size of buffer number 1, we increase the value of s0. however, when we increase the size of buffer number 1, we also increase the value of s4. if the size of buffer number 1 is too large, then the driver will not have enough time to perform tasks s2, s3, s4, s5 and s6. the result is that there will be delay from the execution of task c9 until the execution of task s8. a perfectly timed system will have the values for s5 and s7 at a minimum. an average increase in performance can be achieved if the general guidelines of buffer sizes in figure 2 is fol- lowed. however, as was noted earlier, the correct sizing for buffers will depend upon the expected message size. there are two problems with relating expected message size with the correct buffer sizing: 1. message sizes cannot always be accurately predicted, since a single application may expect different message sizes at different times, therefore, the buffer sizes chosen will not always maximize throughput. 2. within a single application, message sizes might be somewhat predictable, but when the same driver is to be shared with multiple applications, there may not be a common predictable message size. additional problems occur when trying to define the correct sizing because the correct size also depends upon the interrupt latency, which may vary from system to system, depending upon both the hardware and the software installed in each system. in order to deal with the unpredictable nature of the message size, the driver can implement a self tuning descriptor number before the frame arrived after the frame has arrived comments (after frame arrival) own stp enp* own stp enp* 111x011bytes 1 ? 100 2 1 0 x 0 0 0*** discarded buffer 3 0 0 x 0 0 ?** discarded buffer 4 1 1 x 1 1 x controller ? s current location 5 1 0 x 1 0 x not yet used 6 0 0 x 0 0 x not yet used etc. 1 1 x 1 1 x not yet used
am79c961a 197 mechanism that examines the amount of time spent in tasks s5 and s7 as such: while the driver is polling for each descriptor, it could count the number of poll oper- ations performed and then adjust the number 1 buffer size to a larger value, by adding ? t ? bytes to the buffer count, if the number of poll operations was greater than ? x ? . if fewer than ? x ? poll operations were needed for each of s5 and s7, then the software should adjust the buffer size to a smaller value by, subtracting ? y ? bytes from the buffer count. experiments with such a tuning mechanism must be performed to determine the best values for ? x ? and ? y. ? note whenever the size of buffer number 1 is adjusted, buffer sizes for buffer number 2 and buffer 3 should also be adjusted. in some systems the typical mix of receive frames on a network for a client application consists mostly of large data frames, with very few small frames. in this case, for maximum efficiency of buffer sizing, when a frame arrives under a certain size limit, the driver should not adjust the buffer sizes in response to the short frame. an alternative lapp flow - the two interrupt method an alternative to the above suggested flow is to use two interrupts, one at the start of the receive frame and the other at the end of the receive frame, instead of just looking for the srp interrupt as was described above. this alternative attempts to reduce the amount of time that the software ? wastes ? while poll- ing for descriptor own bits. this time would then be available for other cpu tasks. it also minimizes the amount of time the cpu needs for data copying. this savings can be applied to other cpu tasks. the time from the end of frame arrival on the wire to delivery of the frame to the application is labeled as frame latency. for the one-interrupt method, frame latency is minimized, while cpu utilization increases. for the two-interrupt method, frame latency becomes greater, while cpu utilization decreases. note that some of the cpu time that can be applied to non-ethernet tasks is used for task switching in the cpu. one task switch is required to swap a non-ether- net task into the cpu (after s7a) and a second task switch is needed to swap the ethernet driver back in again (at s8a). if the time needed to perform these task switches exceeds the time saved by not polling descriptors, then there is a net loss in performance with this method. therefore, the new word method im- plemented should be carefully chosen. figure 3 shows the event flow for the two-interrupt method. figure 4 shows the buffer sizing for the two-interrupt method. note that the second buffer size will be about the same for each method. there is another alternative which is a marriage of the two previous methods. this third possibility would use the buffer sizes set by the two-interrupt method, but would use the polling method of determining frame end. this will give good frame latency but at the price of very high cpu utilization. and still, there are even more compromise positions that use various fixed buffer sizes and effectively, the flow of the one-interrupt method. all of these compro- mises will reduce the complexity of the one-interrupt method by removing the heuristic buffer sizing code, but they all become less efficient than heuristic code would allow.
198 am79c961a buffer #3 buffer #2 buffer #1 ethernet wire activity: ethernet controller activity: software activity: s10: driver sets up tx descriptor. s9: application processes packet, generates tx packet. s8: driver calls application to tell application that packethas arrived. s7: driver is swapped out, allowing a non-ethernet application to run. s6: driver copies data from buffer #2 to the application buffer. s5: driver polls descriptor #2. s4: driver copies data from buffer #1 to the application buffer. s3: driver writes modified application pointer to descriptor #3. s2: driver call to application to get application buffer pointer. s1: interrupt latency. s0: driver is idle. } n2:eom n0: packet preamble, sfd and destination address are arriving. { packet data arriving } } } c9: controller writes descriptor #3. c8: controller is performing intermittent bursts of dma to fill data buffer #3. c7: controller writes descriptor #2. c6: "last chance" lookahead to descriptor #3 (own). c5: controller is performing intermittent bursts of dma to fill data buffer # 2 c3: srp interrupt is generated. c2: controller writes descriptor #1. c1: controller is performing intermittent bursts of dma to fill data buffer #1 . c0: lookahead to descriptor #2. n1: 64th byte of packet data arrives. c10: erp interrupt is generated. } s8a: interrupt latency. } s7a: driver interrupt service routine executes return. c4: lookahead to descriptor #3 (own). 19364b-89 figure 3. lapp timeline for two-interrupt method
am79c961a 199 descriptor #1 descriptor #2 descriptor #3 descriptor #4 descriptor #5 descriptor #6 descriptor #7 descriptor #8 descriptor #9 own = 1 stp = 1 size = header_size (minimum 64 bytes) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = 1518 - (s1+s2+s3+s4+header_size) own = 1 stp = 1 size = header_size (minimum 64 bytes) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = 1518 - (s1+s2+s3+s4+header_size) own = 1 stp = 1 size = header_size (minimum 64 bytes) own = 1 stp = 0 size = s1+s2+s3+s4 own = 0 stp = 0 size = 1518 - (s1+s2+s3+s4+header_size) a = expected message size in bytes s1 = interrupt latency s2 = application call latency s3 = time needed for driver to write to third descriptor s4 = time needed for driver to copy data from buffer #1 to application buffer space s6 = time needed for driver to copy data from buffer #2 to application buffer space note that the times needed for tasks s1, s2, s3, s4, and s6 should be divided by 0.8 microseconds to yield an equivalent number of network byte times before subtracting these quantities from the expected message size a. 19364b-90 figure 4. lapp 3 buffer grouping for two-interrupt method
200 am79c961a
appendix f am79c961a 201 some characteristics of the xxc56 serial eeproms switching characteristics of a typical xxc56 serial eeprom interface applicable over recommended operating range from ta = ? 40 c to +85 c, vcc = +1.8 v to +5.5 v, cl = 1 ttl gate and 100 pf (unless otherwise noted ) notes: 1. the sk frequency specifies a minimum sk clock period of 2 s, therefore in an sk clock cycle t skh + t skl must be greater than or equal to 2 s. for example, if the t skl = 500 ns then the minimum t skh = 1.5 s in order to meet the sk frequency specification. 2. cs must be brought low for a minimum of 500 ns (t cs ) between consecutive instruction cycles. parameter symbol parameter description test conditions min max unit f sk sk clock frequency 0 0.5 mhz t skh sk high time (note 1) 500 ns t skl sk low time (note 1) 500 ns t cs minimum cs low time (note 2) 500 ns t css cs setup time relative to sk 100 ns t dis di setup time relative to sk 200 ns t csh cs hold time relative to sk 0 ns t dih di hold time relative to sk 200 ns t pd1 output delay to ? 1 ? ac test 1000 ns t pd0 output delay to ? 0 ? ac test 1000 ns t sv cs to status valid ac test 1000 ns t df cs to do in high impedance ac test; cs = v il 200 ns t wp write cycle time 10 ms endurance number of data changes per bit typical 100,000 cycles
202 am79c961a instruction set for the xxc56 series of eeproms note: 1. this is the minimum sk period. address data instruction sb op code x8 x16 x8 x16 comments read 1 10 a8 ? a0 a7 ? a0 reads data stored in memory, at specified address ewen 1 00 11xxxxxxx 11xxxxxx write enable must precede all programming modes erase 1 11 a8 ? a0 a7 ? a0 erases memory location an ? a0 write 1 01 a0 ? a0 a7 ? a0 d7 ? d0 d15 ? d0 writes memory location an ? a0 eral 1 00 10xxxxxxx 10xxxxxx erases all memory locations. valid only at v cc = 4.5 v to 5.5 v wral 1 00 01xxxxxxx 01xxxxxx d7 ? d0 d15 ? d0 writes all memory locations. valid when v cc = 5.0 v 10% and disable register cleared ewds 1 00 00xxxxxxx 00xxxxxx disables all programming instructions do (program) v ih v il v ih v il v ih v il v oh v ol v oh v ol do (read) di sk cs status valid 1 s (1) t css t skh t skl t csh t dis t dih t pdo t pdi t df t df t sv 19364b-91 typical xxc56 series serial eeprom control timing
appendix g am79c961a 203 am79c961a pcnet-isa ii silicon errata report am79c961a rev fd silicon status the items below are the known errata for rev fd silicon. rev fd silicon is the production silicon. note: a signal followed by "*" indicates active low; i.e., master*. the description section of this document gives an external description of the problem. the implication section gives an explanation of how the pcnet-isa ii controller behaves and its impact on the system. the work-around section describes a work around for the problem. the status section indicates when and how the problem will be fixed. current package marking for this revision: line 1: line 2: pcnet(tm)-isa ii line 3: am79c961akc (assuming package is pqfp) line 4: fd line 5: (c) 1993 amd value of chip identification registers, csr89+csr88 [31:0] for this revision = 32261003h. 1) false babl errors generated description: the pcnet-isa ii fd device will intermittenly give babl error indications when the network traffic has frames equal to or greater than 1518 bytes. implication: false babl errors on the receiving station can be passed up to the upper layer software if pcnet-isa ii fd device is just coming out of deferral and the multi-purpose counter used to count the number of bytes re-cevied reaches 1518 at the same time. if the network is heavily loaded with full-size frames, then the probability of a false babl error is high. work-around: there are two possible work-arounds. 1. if the user has no intention to transmit frames larger than 1518 bytes, then the babl bit may be masked to ignore babble errors. in this case the false babble error will not cause an interrupt, nor will it be passed to the higher level software. 2. check to see if the device is transmitting in isr (interrupt service routine), which is induced by the babl error. the bcrs which control the led settings can be programmed to indicate a transmit activity, assuming the interrupt latency is not longer than one mininum ifg (inter-frame gap) time. if (isr_latency < 9.6 us) true_bable_err = babl * ( tint + xmt_led) { i.e. false_bable_err = ~ (babl * ( tint + xmt_led))} else cannot tell if the babl error is true or false just by reading babl, tint, xmt_led bits in isr. status: no current plan to fix this item.
204 am79c961a 2) drq inactive to master* inactive time description: the data sheet lists a minimum limit of 40ns for the time that drq goes inactive until master* goes inactive. during the course of device characterization a minimum value of less than 40ns has been observed. the lower limit for this parameter therefore has been changed to 30ns. (drq inactive to master* inactive time). implication: there is no jeopardy because of this change. the device tristates its active command, sbhe, sa, and la lines before master* goes inactive. work-around: none required. status: data sheet limit will be changed. there will be no change to the silicon. 3) drq inactive to command, sbhe*, sa0-9 and la17-23 tristated. description: the data sheet lists a maximum limit of 0ns for the time that drq goes inactive until command, sbhe*, sa0-9 and la17-23 signals tristate. during the course of device characterization a maximum value of more than 0ns has been observed. the upper limit for this parameter therefore has been changed to 10ns. (drq inactive to command, sbhe*, sa0-9 and la17-23 tristated) implication: there is no jeopardy because of this change. the master* which controls the io on the bus goes inactive after this time. work-around: none required. status: data sheet limit will be changed. there will be no change to the silicon.
am79c961a 205 the contents of this document are provided in connection with advanced micro devices, inc. ( ? amd ? ) products. amd makes no representations or warranties with respect to the accuracy or completeness of the contents of this publication and reserves the right to make changes to speci-fic ations and product descriptions at any time without notice. no license, whether express, implied, arising by estoppel or otherwise, to any in-tellectual property righ ts is granted by this publication. except as set forth in am ? s standard terms and conditions of sale, amd assumes no liability whatsoever, and disclaims any express or implied warranty, re lating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particular purpose, or infringement of an y intellectual property right. amd ? s products are not designed, intended, authorized or warranted for use as components in systems intended for surgical implant i nto the body, or in other appli- cations intended to support or sustain life, or in any other application in which the failure of amd's product could create a s ituation where personal injury, death, or severe property or environmental damage may occur. amd reserves the right to discontinue or make changes to its products at any time without notice. trademarks copyright ? 2000 advanced micro devices, inc. all rights reserved. amd, the amd logo, and combinations thereof are trademarks of advanced micro devices, inc. pcnet, pcnet-isa and magic packet are trademarks of advanced micro devices, inc. product names used in this publication are for identification purposes only and may be trademarks of their respective companies .
206 am79c961a

▲Up To Search▲

Price & Availability of AM79C961AKIW

	To Download AM79C961AKIW Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .